MySQL Bugs: #65368: Japanese characters utf8 bin collide when they should not

Bug #65368	Japanese characters utf8 bin collide when they should not
Submitted:	18 May 2012 21:27	Modified:	19 Jan 2013 20:22
Reporter:	Thomas Jannaud	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: InnoDB storage engine	Severity:	S2 (Serious)
Version:	5.5.20	OS:	MacOS
Assigned to:		CPU Architecture:	Any
Tags:	collide, japanese, Kanji, utf8

Description:
I have a table called "kanjis" with column kanji	varchar(1)	utf8_bin
Some characters won't be inserted in it: 

How to repeat:
I wont give my table, this is an industry application, sorry :(
Inserting those kanjis in an empty table pose no problem, so I guess somewhere there is a problem

Suggested fix:
do some debug ! :)

Please, check if the same problem still happens with a newer version, 5.5.24. 

If it does, please, try to create a small repeatable test case, or send exact CREATE TABLE and example of INSERTs that do not work.

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".

Hi
This is not exactly what you want but it is on the right track I think :
Here is a kanji that I can't put in a 'text' column :

Thank you for the feedback.

Your last message was corrupted. Also we can not solve your problem without having repeatable test case. Please try to create one: we need SHOW CREATE for problem table and query which fails.

Please also check your character-set related options and terminal settings.

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".