summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorJarek Glowacki <jarekwg@outlook.com>2016-01-03 23:21:50 +1100
committerTim Graham <timograham@gmail.com>2016-01-04 10:35:45 -0500
commitd8b651a544696e586bcc941335420ff9b7bf4fb5 (patch)
tree5b139725fc491a61ed33c3a6ac92b235690c69db /docs
parent6a298b220a326a6fa9f2807ab98b7e47a4d9ccd1 (diff)
Added missing step to transitioning squashed migrations.
Diffstat (limited to 'docs')
-rw-r--r--docs/topics/migrations.txt11
1 files changed, 6 insertions, 5 deletions
diff --git a/docs/topics/migrations.txt b/docs/topics/migrations.txt
index db52665067..01b5404fd6 100644
--- a/docs/topics/migrations.txt
+++ b/docs/topics/migrations.txt
@@ -614,12 +614,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