[1.8.x] Fixed #25168 -- Documented how to avoid foreign key constraint error after upgrading to 1.8.
Backport of 70912e137d
from master
This commit is contained in:
parent
57615516bc
commit
466950fa98
|
@ -1169,6 +1169,12 @@ Miscellaneous
|
||||||
automatically faked if all tables created in an initial migration already
|
automatically faked if all tables created in an initial migration already
|
||||||
existed.
|
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:
|
.. _deprecated-features-1.8:
|
||||||
|
|
||||||
Features deprecated in 1.8
|
Features deprecated in 1.8
|
||||||
|
|
Loading…
Reference in New Issue