{"id":7241,"date":"2012-09-04T16:52:58","date_gmt":"2012-09-04T11:22:58","guid":{"rendered":"http:\/\/www.tothenew.com\/blog\/?p=7241"},"modified":"2012-09-23T18:00:44","modified_gmt":"2012-09-23T12:30:44","slug":"toggling-foreign-key-checks-in-mysql","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/toggling-foreign-key-checks-in-mysql\/","title":{"rendered":"Toggling foreign key checks in MySQL"},"content":{"rendered":"

Recently in my project, we needed to import database dumps of a legacy database in MySQL, which was involved in a nested relationship where one tuple could be the parent record of another tuple. We created the appropriate domain structure and checked that the foreign key references were created accordingly. All well and good.
\n
\nSo we started to restore the dump for the database. But soon problems started arising when certain records had references to records that were not yet created i.e, that is some records were being assigned parents that did not exist. We needed a way to turn of foreign key checking for some time. So after taking a look at the MySQL documentation (http:\/\/dev.mysql.com\/doc\/refman\/5.1\/en\/innodb-foreign-key-constraints.html<\/a>), I stumbled across a way to turn off foreign key checking by running the following command:
\n
\n[code]mysql> SET FOREIGN_KEY_CHECKS = 0
\nmysql> SOURCE fakeDB
\nmysql> SET FOREIGN_KEY_CHECKS = 1[\/code]
\n
\nSo there it was. We had happily imported our legacy database with all the foreign key checks intact.
\n
\nIf you’re not sure about the status of foreign key checking in your MySQL instance, you can use the following command to check the status:
\n[code]mysql> select * from INFORMATION_SCHEMA.GLOBAL_VARIABLES where VARIABLE_NAME like ‘FOREIGN_KEY_CHECKS’;[\/code]
\n
\nHope this helps.
<\/p>\n","protected":false},"excerpt":{"rendered":"

Recently in my project, we needed to import database dumps of a legacy database in MySQL, which was involved in a nested relationship where one tuple could be the parent record of another tuple. We created the appropriate domain structure and checked that the foreign key references were created accordingly. All well and good. So […]<\/p>\n","protected":false},"author":33,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":0,"footnotes":""},"categories":[1],"tags":[943,76,944],"class_list":["post-7241","post","type-post","status-publish","format-standard","hentry","category-technology","tag-foreign-key-check","tag-mysql","tag-toggle-foreign-key-check"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t