Import Error: 40101 SET @OLD_CHARACTER_SET_CLIENT =@ @CHARACTER_SET
method to enter: Mysqluse test; MySQL source c:/test.sql Import data, if the target database or table is the UTF-8 character set, and the import SQL has Chinese, may be garbled in the final result, at this point, just add the following in the first line of the imported SQL file. /*!40101 SET NAMES UTF8 * *; Reproduced in the following content: use
Methods to import:
| The code is as follows |
Copy Code |
Mysql>use test; Mysql> Source C:/test.sql |
When importing data, if the target database or table is in the UTF-8 character set, and there is Chinese in the import SQL, there may be garbled in the final result, just add the following in the first row of the imported SQL file.
/*!40101 SET NAMES UTF8 * *;
Method Two
Problem: Because the 4n version of the database is encoded as a latin1,5n version of the database encoded as UTF8. caused.
Remove the following code
| The code is as follows |
Copy Code |
/*!40101 SET @OLD_CHARACTER_SET_CLIENT =@ @CHARACTER_SET_CLIENT * *; /*!40101 SET @OLD_CHARACTER_SET_RESULTS =@ @CHARACTER_SET_RESULTS * *; /*!40101 SET @OLD_COLLATION_CONNECTION =@ @COLLATION_CONNECTION * *; /*!40101 SET NAMES UTF8 * *; |
Use phpMyAdmin import, file character Set selection latin1, everything is OK.
Experience: Use phpMyAdmin to export in default state, save the exported UTF8 encoded file as an ANSI encoding in Notepad.
Open a text file, replacing all GBK as Latin1
Actually, I just took that part
| The code is as follows |
Copy Code |
/*!40101 SET @OLD_CHARACTER_SET_CLIENT =@ @CHARACTER_SET_CLIENT * *; /*!40101 SET @OLD_CHARACTER_SET_RESULTS =@ @CHARACTER_SET_RESULTS * *; /*!40101 SET @OLD_COLLATION_CONNECTION =@ @COLLATION_CONNECTION * *; /*!40101 SET NAMES UTF8 * *;
|
get rid of it and execute successfully.
Other methods
Use phpMyAdmin import, file character Set selection latin1, everything is OK.
Experience: Use phpMyAdmin to export in default state, save the exported UTF8 encoded file as an ANSI encoding in Notepad.
Open a text file, replacing all GBK as Latin1
Your own way of summarizing
You can package the database directly, and then put it in your MySQL data directory to resolve this approach.