test0908
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Added a warning about nonexistent FK constraints when unmigrated apps depend on migrated ones. 

Thanks NotSqrt for the report; refs #23741.
This commit is contained in:
Tim Graham 2014-11-04 07:25:35 -05:00
parent 36f514f065
commit f0ff452451
1 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/topics/migrations.txt Normal file → Executable file
View File

@ -213,8 +213,13 @@ will be.
Be aware, however, that unmigrated apps cannot depend on migrated apps, by the Be aware, however, that unmigrated apps cannot depend on migrated apps, by the
very nature of not having migrations. This means that it is not generally very nature of not having migrations. This means that it is not generally
possible to have an unmigrated app have a ForeignKey or ManyToManyField to possible to have an unmigrated app have a ``ForeignKey`` or ``ManyToManyField``
a migrated app; some cases may work, but it will eventually fail. to a migrated app; some cases may work, but it will eventually fail.
.. warning::
Even if things appear to work with unmigrated apps depending on migrated
apps, Django may not generate all the necessary foreign key constraints!
This is particularly apparent if you use swappable models (e.g. This is particularly apparent if you use swappable models (e.g.
``AUTH_USER_MODEL``), as every app that uses swappable models will need ``AUTH_USER_MODEL``), as every app that uses swappable models will need