I know it's in unicode now, but I think the problem was that MySQL still
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 mess
things up that are already in unicode. I saw on
"If you will configure MySQL
4.1 to use utf8 by default and just start it with MySQL 4.0 latin1 tables
you're likely to trash your data, as there is no charset information in old
tables and MySQL 4.1 will assume the data is in unicode. So do not change
character set straight ahead but run 4.1 with same charset as 4.0 before and
use ALTER TABLE to convert tables to 4.1 format - this has character set
information so you should be safe."
2009/5/18 Brion Vibber <brion(a)wikimedia.org>
El 5/16/09 12:20 PM, Gerard Meijssen escribió:
An upgrade to MySQL 6 would make a big difference for language and
support. We need to first make use of
improvements that are out there
we consider "roling our own".
I think I'd recommend against upgrading our production databases to an
alpha development release at this time. :)
The addition of full UTF-8 support is pleasing, and eventually may be a
factor in future upgrades when some day it's released.
-- brion vibber (brion @ wikimedia.org
Wikitech-l mailing list