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

[1.7.x] Update squashmigration docs to also mention circ dep errs (refs #23337)

This commit is contained in:
Andrew Godwin 2014-08-21 19:17:25 -07:00
parent f8aa2aa486
commit fbe4507623
1 changed files with 10 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -483,11 +483,16 @@ work::
you can delete them. you can delete them.
Note that model interdependencies in Django can get very complex, and squashing Note that model interdependencies in Django can get very complex, and squashing
may occasionally result in an optimized migration that doesn't work or is may result in migrations that do not run; either mis-optimized (in which case
impossible to run. When this occurs, you can re-try with ``--no-optimize``, but you can try again with ``--no-optimize``, though you should also report an issue),
please `file a bug report <https://code.djangoproject.com/newticket>`_ either or with a ``CircularDependencyError``, in which case you can manually resolve it.
way detailing the models and their relationships so we can improve the
optimizer to handle your case. To manually resolve a ``CircularDependencyError``, break out one of
the ForeignKeys in the circular dependency loop into a separate
migration, and move the dependency on the other app with it. If you're unsure,
see how makemigrations deals with the problem when asked to create brand
new migrations from your models. In a future release of Django, squashmigrations
will be updated to attempt to resolve these errors itself.
Once you've squashed your migration, you should then commit it alongside the Once you've squashed your migration, you should then commit it alongside the
migrations it replaces and distribute this change to all running instances migrations it replaces and distribute this change to all running instances