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

Refs #24109 -- Doc'd the elidable feature in squashing migrations docs.

This commit is contained in:
Ed Morley 2017-01-17 13:43:21 +00:00 committed by Tim Graham
parent f01ad1cb6a
commit d1eda9b4ad
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/topics/migrations.txt
View File

@ -582,8 +582,8 @@ Once the operation sequence has been reduced as much as possible - the amount
possible depends on how closely intertwined your models are and if you have possible depends on how closely intertwined your models are and if you have
any :class:`~django.db.migrations.operations.RunSQL` any :class:`~django.db.migrations.operations.RunSQL`
or :class:`~django.db.migrations.operations.RunPython` operations (which can't or :class:`~django.db.migrations.operations.RunPython` operations (which can't
be optimized through) - Django will then write it back out into a new set of be optimized through unless they are marked as ``elidable``) - Django will then
migration files. write it back out into a new set of migration files.
These files are marked to say they replace the previously-squashed migrations, These files are marked to say they replace the previously-squashed migrations,
so they can coexist with the old migration files, and Django will intelligently so they can coexist with the old migration files, and Django will intelligently