Must be a coding problem (UTF8 or GBK), but it is not necessarily the SQL file data, SQL file encoding problem, it may be the Import tool (encoding) problem
There are several ways to import MySQL
1234SSC Prestige Platform "q:737888396" honor Platform "q:737888396" Emperor Prestige Platform "q:737888396" honor Platform "q:737888396" Emperor Prestige Platform "q:737888396" Emperor Prestige platform "Q : 737888396 "Emperor Prestige Platform" q:737888396 "Emperor Prestige Platform" q:737888396 "Emperor Prestige Platform" q:737888396 "Emperor Prestige Platform" q:737888396 "Emperor Prestige platform" q:737888396 " Emperor Prestige platform "q:737888396" Emperor Prestige Platform "q:737888396" Emperor Prestige Platform "q:737888396" honor Platform "q:737888396" Emperor Prestige Platform "q:737888396" Emperor Prestige platform "Q : 737888396 "Emperor Prestige Platform" q:737888396 "Emperor Prestige Platform" q:737888396 "Emperor Prestige Platform" q:737888396 "Emperor Prestige Platform" q:737888396 "Emperor Prestige platform" q:737888396 " Emperor Prestige platform "q:737888396" Emperor Prestige Platform "q:737888396" Emperor Prestige Platform "q:737888396" honor Platform "q:737888396" Emperor Prestige Platform "q:737888396" Emperor Prestige platform "Q : 737888396 "
- Windows down cmd
- Navicat Import
- Navicat Console Tool Import ...
- Navicat new query, load SQL, execute ...
This error occurs because the character set of the CMD command-line tool in Windows is not UTF8, loaded and executed with the Navicat query tool, the import succeeds
MySQL import Chinese times error 1366