You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We encountered an issue with the default SQL Server behaviour of treating String parameters (part of a prepared statement) being considered as NVARCAR on the executed statement.
And this is due to the connection property named sendStringParametersAsUnicode having the default value of true.
See this issue with the details on the Java implementation and how it was solved.
And this is a similar example, using Tiberius library, which it is still affected by that SQL Server behavior.
Therefore, is sendStringParametersAsUnicode connection property being supported?
I believe not, although it should be easily added.
Thanks!
The text was updated successfully, but these errors were encountered:
Hi everyone!
We encountered an issue with the default SQL Server behaviour of treating
String
parameters (part of a prepared statement) being considered asNVARCAR
on the executed statement.And this is due to the connection property named
sendStringParametersAsUnicode
having the default value oftrue
.See this issue with the details on the Java implementation and how it was solved.
And this is a similar example, using Tiberius library, which it is still affected by that SQL Server behavior.
Therefore, is
sendStringParametersAsUnicode
connection property being supported?I believe not, although it should be easily added.
Thanks!
The text was updated successfully, but these errors were encountered: