I know it's in unicode now, but I think the
problem was that MySQL
assumes that it's in latin1 -- when you upgrade to MySQL 4.1, as I
understand it, some of the text is "converted" to unicode which can
things up that are already in unicode. I saw on
"If you will
4.1 to use utf8 by default and just start it with MySQL 4.0 latin1
you're likely to trash your data, as there is no charset information
tables and MySQL 4.1 will assume the data is in unicode. So do not
character set straight ahead but run 4.1 with same charset as 4.0
use ALTER TABLE to convert tables to 4.1 format - this has character
information so you should be safe."
Or you can use --character-set-server (=binary in our case).