Fixed #25390 -- Allowed specifying a start migration in squashmigrations

Thanks Tim Graham for the review.
This commit is contained in:
Markus Holtermann 2015-09-12 17:18:24 +10:00
parent 5aa55038ca
commit 43f2eb7ef3
5 changed files with 88 additions and 18 deletions

View file

@ -572,7 +572,7 @@ possible depends on how closely intertwined your models are and if you have
any :class:`~django.db.migrations.operations.RunSQL`
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
initial migration files.
migration files.
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