1
0
mirror of https://github.com/django/django.git synced 2025-05-05 06:27:31 +00:00

[1.10.x] Refs #24109 -- Doc'd the elidable feature in squashing migrations docs.

Backport of d1eda9b4ad47c7773e65d90fd882e9d07759fe41 from master
This commit is contained in:
Ed Morley 2017-01-17 13:43:21 +00:00 committed by Tim Graham
parent f3af0acb09
commit 04446b60f2

View File

@ -584,8 +584,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