We like to create a database that stores CHARs as "UTF16-LE", but literally ALL (!) collations listed with -l say they are incompatible with "UTF-16LE". So what is the magic trick...?
asked 05 Mar '15, 05:16
AFAIK, in SQL Anywhere neither CHAR nor NCHAR data types can use UTF-16 to store values. When using UNICODE you are restricted to UTF-8 (which will often need much lesser storage) - in contrast to say, MS SQL Server using UTF-16 for NCHAR data IIRC.
Cf. the qoute from the doc topic "International languages and character sets":
(Note: I may be mixing - as usually - the terms "character sets"/"encodings"/"collations"...)