Bug #88188 Incorrect conversion from string to bytes when using GB18030 charset
Submitted: 23 Oct 2017 15:55 Modified: 23 Oct 2017 15:56
Reporter: Jose Ramirez Ruiz Email Updates:
Status: Verified Impact on me:
None 
Category:Connector / NET Severity:S3 (Non-critical)
Version:6.10.3 OS:Any
Assigned to: CPU Architecture:Any

[23 Oct 2017 15:55] Jose Ramirez Ruiz 
Description:
When creating a connection and table with charset=GB18030 the inserted values will sometimes be incorrect.

Behavior indicates that encoding is not being properly handled.
The result of executing _encoding.GetBytes() in MySqlPacket.WriteStringNoNull() is not always correct when using said charset. 

How to repeat:
The bug is intermittent and is very hard to reproduce. Multiple executions of the same code is required.

Try opening a connection with charset GB18030 and to create a table with same charset. Upon inserting values to the table the error may occur.