Skip to content

Is sendStringParametersAsUnicode connection property being supported? #367

@dxps

Description

@dxps

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!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions