mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-10-31 09:41:08 +00:00
Code Issues 32 Releases Wiki Activity

[1.7.x] Fixed #23090: Document and enforce not double-squashing migrations

Browse Source
This commit is contained in:
Andrew Godwin
2014-07-29 10:02:59 -07:00
parent 0a4fbf4e13
commit 3deddc2fdf
2 changed files with 19 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
docs/topics/migrations.txt
View File

@@ -487,6 +487,23 @@ please `file a bug report <https://code.djangoproject.com/newticket>`_ either
way detailing the models and their relationships so we can improve the
optimizer to handle your case.
Once you've squashed your migration, you should then commit it alongside the
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:
- 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)
.. note::
Once you've squashed a migration, you should not then re-squash that squashed
migration until you have fully transitioned it to a normal migration.
.. _migration-serializing:
Serializing values