Unicode support in ODBC API - #1018
Open
MEO265 wants to merge 5 commits into
Open
Conversation
MEO265
marked this pull request as ready for review
July 7, 2026 14:53
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Compile nanodbc with the flag
NANODBC_USE_UNICODEfor better Unicode handling.If desired, I can also explain specific decisions, but I think the code comments should explain quite a bit for now.
I was able to test it quite extensively with MS SQL on Windows and Ubuntu, but it would be good if more system combinations were tested. In particular, I’m not entirely sure whether macOS has any special quirks.
Resolves #945 and #944. And probably resolves #301, #479, #966 , #427, #410, #301 and #273
Thanks in advance for taking a look. I know that, given the number of changes, reviewing it will take quite a bit of effort.
The instability observed in an earlier version was caused by the ASCII driver being used for PostgreSQL.
For auto closing:
encodingprameter #944