Hello.
Please send us an output of the following statement: SHOW VARIABLES LIKE '%char%'; See: http://dev.mysql.com/doc/mysql/en/charset-conversion.html Bruce Dembecki <[EMAIL PROTECTED]> wrote: > Hi! We have a problem converting our 4.0 text columns from a Hong Kong > database to 4.1. In order to get the conversions to work generally speaking > we build our databases with default character set utf8 - it means the German > products still work, and the English ones, and the Chinese ones, and the.... > > Anyway, we ran into a problem on the Hong Kong platform where the text > column imports as a single space to 4.1... If I look at the data in 4.0 I > see actual text (I suppose, it's mostly jibberish on my screen), while in > 4.1 all I have after the import is a single space character. > > If I change the column type to blob (from text) I can get the data imported > without problem, except that the data is now in a blob column. If I try to > alter the table to a text column, I am left with the single spaces again. > > Looking at the data that does get affected (not all records suffer this > fate, just some) it appears that they have multiple languages, for example > Chinese or more often Japanese, together with something like an email > address which is written in latin type characters. I can post a new entry > through the webapp with mixed languages, it's just the export/import that > seems to be be letting us down - or converting the blob to a text in 4.1 > after the fact. > > I even tried building a duplicate table format and doing an INSERT SELECT > where the source is a blob and the target is a text, and that also fails. > > Clearly I can't convert the rest of my databases if there is a chance that > our message bodies will be munged.... With about 100 databases each with 60 > tables it's not even going to be easy to try and script it in such a way > that I could do a dump and an import with something changing the table type > in the .sql file from text to blob, let alone the time it will take us to > first test the Application and web servers to see if making the change to a > blob column will affect us in any way. > > Do I need to be doing all this work... Is there something I have done > incorrectly? Is this a bug that someone is fixing and will go away next > version? > > I can provide the dump files if someone wants to test... Let me know. > > Best Regards, Bruce > > -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
