Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is sendStringParametersAsUnicode connection property being supported? #367

Open
dxps opened this issue Oct 30, 2024 · 0 comments
Open

Is sendStringParametersAsUnicode connection property being supported? #367

dxps opened this issue Oct 30, 2024 · 0 comments

Comments

@dxps
Copy link

dxps commented Oct 30, 2024

Hi everyone!

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant