MySQL garbled file
Move the server this afternoon; the transfer data was killed. Because the data is upgraded to a higher version through MySQL's low version, there are many problems in the relocation process.
Because the default character set used to start the database is a bit of a problem with gb2312 upgraded MySQL, and finally the setchar=gb2312 of the data is taken out;
Then setchar the text set depends on your MySQL my.cnf when the default character set file is used, if the default is gb2312 no way you will setchar remove your character or gb2312
So you can change setchar=gb2312 to setchar=latin1. The default startup character set for my.cnf files is removed from the new startup MySQL
http://www.bkjia.com/PHPjc/508510.html www.bkjia.com true http://www.bkjia.com/PHPjc/508510.html techarticle MySQL garbled file this afternoon moved the server; the transfer data was killed because the data was upgraded to a higher version through MySQL's low version;