Added additional unicode letter points #2329
Conversation
| "invalid ' sql" | ["invalid", " ", "'", " ", "sql"] | ||
|
|
||
|
|
||
| "utf8-〠＠chars works" | ["utf8", "-", "〠＠chars", " ", "works"] |
There was a problem hiding this comment.
Thanks for adding this test.
|
The parse error reproduces during update-sql or update with insert statements of strings containing unicode characters into an ntext or nvarchar column. During initial testing, I used inserts with a value containing one problematic unicode character; this did not show the error because there was nothing to 'parse' with a single character. Special Thanks! Borja Serrano, your comment with a full SQL insert statement in CORE-3269 gave me what I needed to reproduce this bug. Thank you! Example XML Changelog with Insertshttps://app.zenhub.com/files/2019791/e41ea4e8-c4df-430c-9884-0ddef2af0b41/download
Test Environment |
Description
Comments in #1107 listed additional unicode points which cause problems with Japanese chars in sql
Dev Handoff Notes (Internal Use)
Links
Testing
Dev Verification
Ensured existing parser-based tests pass. Did not add additional automated tests since we don't check for every possible char
┆Issue is synchronized with this Jira Bug by Unito