houper888 opened a new issue, #35126: URL: https://github.com/apache/shardingsphere/issues/35126
**When I used Npgsql to read data from ShardingSphere, I found that the Chinese content could never be completely read during the process.**  **After investigation, I learned that Npgsql uses the extended query protocol(binary). The problem is that ShardingSphere while writing text as binary encodes the length as the number of characters a string contains, ignoring the encoding client specified. As an example, string 这是一个测试字符串 has 9 characters (this is what npgsql will get as column's length), while in reality ShardingSphere should send us a 54 byte array (which is correct as that's 27 2-byte characters, 3 characters per a single Chinese character).**  **The length returned here should be based on the encoding required by the client.** -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
