Some errors encountered in MySQL data migration

background

Doing it MYSQL When migrating databases , Some problems , Record these questions , For future reference

sql_mode

Many verifications are combined with this mode There is a direct connection

##  Import sql file , The following error occurred 
MySQL:[Err] 1292 - Incorrect datetime value: '0000-00-00 00:00:00' for column 'CREATE_TIME' at row 1

Cause  

This is due to the current MySQL I won't support it datetime by 0 The state of .

  Check and select the current sql_mode

select @@global.sql_mode;

Solution

Set current sql_mode 

##  At present 
set @@sql_mode = 'STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION';

  Get into mysql Execute the command in the command interface

##  overall situation 
set @@global.sql_mode = 'STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION';

PS: Both of the above methods can temporarily solve the problem , But when the database restarts , Previous modifications will be invalid  

modify my.ini The configuration file  

Only modify the configuration file , To solve this problem forever , stay my.ini Add... To the file

sql_mode = STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION

Re execution  select @@global.sql_mode;

 

 

Always report errors that do not exist in the form

Confirm that the table exists , But there is no error in the query table , At this point, it may be because you think mysql Case sensitive , This configuration can be modified

stay my.ini The following code is added to the file

##  Use this command to view the case sensitive configuration in the current system 
show global variables like '%case%';

## lower_case_file_system  The system is case sensitive - There is no need to change 
## lower_case_table_names  Currently case sensitive , Need to change to 1
+------------------------+-------+
| Variable_name          | Value |
+------------------------+-------+
| lower_case_file_system | OFF   |
| lower_case_table_names | 0     | 
+------------------------+-------+
2 rows in set (0.01 sec)

lower_case_table_names = 1

  After adding configuration , Restart the service and check again

 

Problem solved , If it is not configured in the configuration file , The service will restart next time , Invalidate the previous configuration , There are some problems that are not easy to check , therefore , If it doesn't need to be modified temporarily , Are modified in the configuration file