Skip to content

Conversation

srutzky
Copy link
Contributor

@srutzky srutzky commented Nov 21, 2023

This fixes #515 .

Add "N" prefix to quoted string substitution when preparing SQL for execution. This will change string literals to be interpreted as NVARCHAR (i.e. Unicode / UTF-16) instead of VARCHAR (i.e. an 8-bit encoding, which changes all characters not in the associated code page to "?"s).

PLEASE NOTE: I don't have time to test this fix. If it helps, there are some notes on what should be tested in PR #422 .

Add "N" prefix to quoted string substitution when preparing SQL for execution. This will change string literals to be interpreted as NVARCHAR (i.e. Unicode / UTF-16) instead of an 8-bit encoding (which changes all characters not in the associated code page to "?"s).
@LarnuUK
Copy link

LarnuUK commented Jul 11, 2024

Tested in 6.5.3 and appears to work without issue.

@LarnuUK
Copy link

LarnuUK commented Jun 30, 2025

Retested in 3.8.1 and working as expected.

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

Successfully merging this pull request may close these issues.

Regression of non-ANSI strings handing in 6.2.0
2 participants