From 466950fa981caf4d3149ba39f6b214413df463f3 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Fri, 31 Jul 2015 08:07:16 -0400 Subject: [PATCH] [1.8.x] Fixed #25168 -- Documented how to avoid foreign key constraint error after upgrading to 1.8. Backport of 70912e137d5a6b089f35c662115fb758a00d7002 from master --- docs/releases/1.8.txt | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/releases/1.8.txt b/docs/releases/1.8.txt index 1f44a86af4..1901d7fba4 100644 --- a/docs/releases/1.8.txt +++ b/docs/releases/1.8.txt @@ -1169,6 +1169,12 @@ Miscellaneous automatically faked if all tables created in an initial migration already existed. +* An app *without* migrations with a ``ForeignKey`` to an app *with* migrations + may now result in a foreign key constraint error when migrating the database + or running tests. In Django 1.7, this could fail silently and result in a + missing constraint. To resolve the error, add migrations to the app without + them. + .. _deprecated-features-1.8: Features deprecated in 1.8