Re: Error inserting UTF8 data into primary key (collation & sharp-s)
Posted by: Rick James
Date: March 12, 2011 09:00AM

CHARACTER SET controls storage.
COLLATION controls comparisions.
A 'comparison' is used to decide whether 'weiƟ' is the same as 'weis'.
For utf8_general_ci, they are different.
For utf8_unicode_ci, they are treated the same.

As for why 5.5.9 chose a different collation? I don't know. Suggest you establish a default collation on the database before starting the load. And/or modify the dump file to explicitly set the preferred collation on each table.

These also talk about issues with the sharp-s:
http://forums.mysql.com/read.php?103,388781,389137
http://dev.mysql.com/doc/refman/5.5/en/charset-unicode-sets.html (Search for German)

Options: ReplyQuote


Subject
Views
Written By
Posted
Re: Error inserting UTF8 data into primary key (collation & sharp-s)
3167
March 12, 2011 09:00AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.