On 7/15/05, Bruce Dembecki <[EMAIL PROTECTED]> wrote: > This process has worked for us taking our latin1 4.0 databases and > turning them into utf8 4.1 databases. UTF8 data we had already put in > our 4.0 database despite it's latin1 encoding was correctly exported > out of 4.0 and correctly converted on it's way in to 4.1
Wow! Really? This part amazes me. So the MySQL importing process seems to do the converting of the special characters into the newly-defined encoding format? (from latin1 to utf-8 in my case) See - we do webhosting for clients around the world, and right now our default-encoded MySQL 4.0 databases have Swedish and Hebrew characters in them. I'm concerned that if I dumped them as latin1/default in 4.0, but then imported as utf-8 in 4.1 that the non-ASCII characters would get imported as the wrong encoding. (Assuming, yes, that I would set our new 4.1 databases to do ALL utf-8 in the /etc/my.cnf and gladly take the small performance/size hit.) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
