Hello.
Try to follow the manual. At first you should perfrom an upgrade to 4.0.
If everything is Ok - then move to 4.1. See:
http://dev.mysql.com/doc/mysql/en/upgrading-from-3-23.html
http://dev.mysql.com/doc/mysql/en/upgrading-from-4-0.html
> Yes. I tried. The result is all Chinese words were turned into
> unrecognized characters.
Have a look here:
http://dev.mysql.com/doc/mysql/en/charset-upgrading.html
Chenzhou Cui wrote:
>
>
> YL wrote:
>
>> Did you tried just copy those 3.23 files into a newly installed 4.1 data
>> folder? What's happen?
>>
>>
>
> Yes. I tried. The result is all Chinese words were turned into
> unrecognized characters.
> In my system, there are tens of databases, which include thousands of
> tables. A very large system, I feel.
>
>> ----- Original Message ----- From: "Chenzhou Cui" <ccz@stripped>
>> To: <mysql@stripped>
>> Sent: Friday, September 23, 2005 12:40 AM
>> Subject: MySQL upgrade from 3.x to 4.1 for Chinese databases
>>
>>
>>
>>
>>> Dear all,
>>>
>>> On my server there are thousands of database files contenting Chinese
>>> records. The total data volumn is over 20GB. Is there an easy way to
>>> upgrade the whole system from MySQL 3.23.x to 4.1.x?
>>>
>>> "mysqldump" is NOT a good way for me. It will be a hard and time costing
>>> work. Is it possible to directly use the binary db files, "*.frm",
>>> "*.MYI", "*.MYD", and keep the Chinese support? This is a very big and
>>> important problem facing many Chinese users.
>>>
>>> cheers,
>>> Chenzhou
>>>
>>> --
--
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Gleb Paharenko
/ /|_/ / // /\ \/ /_/ / /__ Gleb.Paharenko@stripped
/_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET
<___/ www.mysql.com
