MySQL #1406

Over the past two days, I have been tossing WordPress, upgrading the system, adding various plug-ins, and then setting up the environment at home to start debugging. Everything went smoothly. Use WordPressDatabaseBa again

Over the past two days, I have been tossing WordPress, upgrading the system, adding various plug-ins, and then setting up the environment at home to start debugging. Everything went smoothly. Use WordPress Database Ba again

Over the past two days, I have been tossing WordPress, upgrading the system, adding various plug-ins, and then setting up the environment at home to start debugging. Everything went smoothly. After using the WordPress Database Backup tool to back up the file, the gz file is sent to my mailbox, but the problem occurs when the company is preparing to import the Backup file, always Report #1406-Data too long for column error. I checked some information and said I want to modify my. ini does not feel credible.

Check the imported SQL file carefully and find that ENGINE = MyISAM AUTO_INCREMENT = 2 DEFAULT CHARSET = latin1 is used for creating each table. The encoding uses latin1, so it is changed to UTF-8. Import again. You can import it, but it is only a part of it. You still cannot import it all. Continue to observe and find that most of the content in the table wp_comments cannot be imported, all these are spam messages (many strange symbols are used in spam messages). The spam messages are deleted and imported successfully.

Finally, we recommend you to query the mysql error code:

English

Chinese

Okay, you can continue to study! :)