Django/django
11
0
Fork 0
Code Pull Requests Projects Releases Activity

[1.9.x] Added missing step to transitioning squashed migrations.

Browse Source 
Backport of d8b651a544696e586bcc941335420ff9b7bf4fb5 from master
This commit is contained in:
Jarek Glowacki 2016-01-03 23:21:50 +11:00 committed by Tim Graham
parent d86870cb6c
commit 6e5d77dc05
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/topics/migrations.txt
View File

@ -626,12 +626,13 @@ migrations it replaces and distribute this change to all running instances
of your application, making sure that they run ``migrate`` to store the change
in their database.
After this has been done, you must then transition the squashed migration to
a normal initial migration, by:
You must then transition the squashed migration to a normal migration by:
- Deleting all the migration files it replaces
- Removing the ``replaces`` argument in the ``Migration`` class of the
squashed migration (this is how Django tells that it is a squashed migration)
- Deleting all the migration files it replaces.
- Updating all migrations that depend on the deleted migrations to depend on
the squashed migration instead.
- Removing the ``replaces`` attribute in the ``Migration`` class of the
squashed migration (this is how Django tells that it is a squashed migration).
.. note::
Once you've squashed a migration, you should not then re-squash that squashed