Also talk about Chinese garbled characters from MySQL4.0 to 4.1 _ MySQL

I am also talking about Chinese garbled text that has been upgraded from MySQL4.0 to 4.1. I think everyone will have this problem.
About several hundred MB of data needs to be imported.

For example, if you want to put the data exported from mysqldump to 4.1, I think there are two methods:

First, set your mysql 4.1 to the gb2312 character set.

Then you open the file to be exported and add the "CREATE" syntax to the file.
Create table sss (
Zxxxxxx
) Character set binary;

In this way, when you export to the new library, char varchar will change to VARBINARY, and then you will change it to gb2312.

This also has a disadvantage. if you have many tables, it may affect performance. You need to modify fields one by one.

I suggest you change the CHAR structure of the CREATE TABLE in the file to BINARY and VARCHAR to VARBINARY so that you still know how to modify the structure.

In general, it will be better to convert it to BINARY before export.