MySQL Bugs: #18288: A few Chinese characters cannot be stored

Bug #18288	A few Chinese characters cannot be stored - Most can
Submitted:	16 Mar 2006 20:03	Modified:	23 Apr 2006 7:55
Reporter:	Joseph Peacock	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	4.1.11	OS:	Windows (Windows 2000)
Assigned to:		CPU Architecture:	Any

Description:
I am attempting to store Chinese text in a table with UTF-8 encoding and utf8_general_ci collation.  After being stored, they are retrieved and displayed on a web page.  On that page, which is properly set to use the UTF-8 character set, about 95% of the characters are correct, but a few are replaced with question marks and boxes.  the fact that most are correct indicates to me that my settings are correct in all places, but perhaps the UTF-8 Character set is incomplete.

Characters that work fine (Hex):
创 (C3A5CB86E280BA)
造 (C3A9E282ACC2A0)
知 (C3A7C5B8C2A5)
牌 (C3A7E280B0C592)

Characters that are not working (Hex):
名 (C3A53F3F)
品 (C3A5E2809C3F)
成 (C3A6CB863F)

I am using ColdFusion MX 7 and the MySQL ODBC connector on a Windows machine.  This is a shared hosting environment, so I may not be able to upgrade anything.

How to repeat:
Create a table with UTF-8 character encoding.  Insert the supplied characters and attempt to display them as described.

Thank you for a problem report. You have to check the latest version, 4.1.18, for proper character set support, anyway. Please, try and inform about the results.

I believe the problem was with the connector used between ColdFusion and MySQL.  The hosting company appeared to be going through the Windows ODBC driver, rather than Connector/J, but I could not get them to explain their exact setup to me.  After moving to a different hosting solution and using Connector/J 3.1.10, the problem has been resolved.

So, can I close this bug report now? If no, please, specify the exact version of the MySQL ODBC driver that was used.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".