Can you automatically create a mysqldump file that doesn't enforce foreign key constraints?
MysqlForeign KeysMysqldumpData ImportMysql Problem Overview
When I run a mysqldump command on my database and then try to import it, it fails as it attempts to create the tables alphabetically, even though they may have a foreign key that references a table later in the file. There doesn't appear to be anything in the documentation and I've found answers like this that say to update the file after it's created to include:
set FOREIGN_KEY_CHECKS = 0;
...original mysqldump file contents...
set FOREIGN_KEY_CHECKS = 1;
Is there no way to automatically set those lines or export the tables in the necessary order (without having to manually specify all table names as that can be tedious and error prone)? I could wrap those lines in a script, but was wondering if there is an easy way to ensure I can dump a file and then import it without manually updating it.
Mysql Solutions
Solution 1 - Mysql
The mysqldump command included with MySQL since version 4.1.1 by default produces a script that turns off the foreign key checks. The following line is included near the top of the dump file:
/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;
The /*!40014 ... */ syntax is a conditional comment that will be executed on MySQL version 4.0.14 and later. The old foreign key checks setting is restored towards the end of the dump file:
/*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */;
Note that the conditional comments are interpreted by the the client (rather than the server). If you load the dump file with a client that doesn't support them, then foreign key checks will not be disabled and you might encounter errors. For best results, I'd suggest loading dump files using the official mysql command line client:
mysql -hserver -uuser -p database < dumpfile.sql
It's also worth noting that if mysqldump is run with the --compact option, then the commands to disable and re-enable the foreign key checks are omitted from the dump file.
Solution 2 - Mysql
Beware. For some reason mysqldump doesn't write the FOREIGN_KEY_CHECKS=0 if the --compact option is used.
Ciao.
Solution 3 - Mysql
If you're using phpMyAdmin when exporting SQL, choose Custom Export Method. Then among the checkbox options, click "Disable foreign key checks". The exported SQL statement will have the disable and enable foreign key checks at the beginning and end of the output file respectively.
It's not "automatic", but you won't have to write the statements yourself for every export.
Solution 4 - Mysql
This may happen if you use --compact as one of your mysqldump command.
--compact includes --skip-comments so instead --compact one should use --skip-add-drop-table --skip-add-locks --skip-disable-keys --skip-set-charset
Solution 5 - Mysql
Beware of your MySQL client you use, with the mysql command, no problem. Dumping:
% mysqldump -u ocp6 -pocp6 ocp6 --single-transaction --result-file=dump.sql
Restoring:
% mysql -u ocp6 -pocp6 ocp6 < dump.sql
Everything's fine.
With the use of another MySQL client (mycli in my situation) to restore the dump-file:
mysql ocp6@:(none)> \. dump.sql
[…]
(1005, 'Can\'t create table `ocp6`.`composition` (errno: 150 "Foreign key constraint is incorrectly formed")')
I assume that mycli do not understand conditional comments.
Solution 6 - Mysql
using --single-transaction means do all in one transaction. That option can not ignore malformed Foreign key constraint.
In any transaction any error will stop continuing query execution. Your problem is that you have a Foreign key constraint to a table which does not exist.