While retriving data, for ANSI app binding SQL_C_CHAR will return data in system default charset (which is GBK for Simplified Chinese Localization), and for UNICODE app will return data in utf8.
If application's charset is different from the above, will causing garbled result.
This issue is the gateway side issue for ODBC driver issue https://gitee.com/openlookeng/hetu-odbc-driver/issues/I1Q6NF?from=project-issue
Connect charset is configurable, and user can choose the charset to meet the app needs.
Gateway are using java character set alias for decoding/encoding, which needs to be mapped to mysql character sets in index_to_charset.properties
A app using charset different from gbk or utf8 will recieve garbled result.
NA
UTF16 are not supported due to high impact
Вход Перед тем как оставить комментарий