The core function of this syntax is to inform the database that the string should be processed using Unicode encoding (such as UTF-16), primarily for matching fields of Unicode types like NVARCHAR.

I have a SQL script encoded in UTF-8 that contains insert statements with unicode strings that are inserting in a NVARCHAR field. When I run this script, the data inserted in the table is malformed.

While polars can only output CSV in UTF-8 encoding, the default encoding in Windows is ANSI. This causes problems as an application may not correctly interpret non-ASCII characters, when they cannot ...