DB drivers should never send strings with invalid encodings to the DB server #4710
Comments
davidnich
added a commit
to qorelanguage/module-sybase
that referenced
this issue
Apr 9, 2023
…codings when the driver does not convert encodings for us
davidnich
added a commit
to qorelanguage/module-sybase
that referenced
this issue
Apr 9, 2023
…codings when the driver does not convert encodings for us
davidnich
added a commit
to qorelanguage/module-sybase
that referenced
this issue
Apr 9, 2023
…codings when the driver does not convert encodings for us
davidnich
added a commit
to qorelanguage/module-sybase
that referenced
this issue
Apr 9, 2023
…codings when the driver does not convert encodings for us
davidnich
added a commit
to qorelanguage/module-sybase
that referenced
this issue
Apr 9, 2023
…codings when the driver does not convert encodings for us
davidnich
added a commit
to qorelanguage/module-sybase
that referenced
this issue
Apr 9, 2023
refs qorelanguage/qore#4710 automatically detect and set character en…
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
like JDBC - only currently Qore'd
jdbcandodbcdrivers do this right - all other drivers respect the user's setting and send string data in the encoding specified even though it may not be correct for the DB server.Qore drivers need to detect the encoding for the DB and send strings in the correct encoding automatically and not depend on the user's encoding choice.
The text was updated successfully, but these errors were encountered: