From afbc5a8b7b41403450e9664b68d7a5c99e1c0c86 Mon Sep 17 00:00:00 2001
From: Alice Heaton <aliceh@aptivate.org>
Date: Sat, 11 Jul 2015 14:19:43 +0100
Subject: [PATCH] InnoDb table and foreign key checks don't work well together
in Django. See
http://stackoverflow.com/questions/6178816/django-cannot-add-or-update-a-child-row-a-foreign-key-constraint-fails
---
django/website/local_settings.py.dev | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/django/website/local_settings.py.dev b/django/website/local_settings.py.dev
index ea47cd35..41f2337f 100644
--- a/django/website/local_settings.py.dev
+++ b/django/website/local_settings.py.dev
@@ -23,7 +23,7 @@ DATABASES = {
'HOST': '', # Set to empty string for localhost. Not used with sqlite3.
'PORT': '', # Set to empty string for default. Not used with sqlite3.
'OPTIONS': {
- "init_command": "SET storage_engine=INNODB",
+ "init_command": "SET storage_engine=INNODB;SET foreign_key_checks = 0;",
}
}
}
--
GitLab