#36141: After double squashing migrate command fails with
InconsistentMigrationHistory
---------------------------------+--------------------------------------
Reporter: Jacob Walls | Owner: (none)
Type: Bug | Status: new
Component: Migrations | Version: dev
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+--------------------------------------
Changes (by Sarah Boyce):
* cc: Georgi Yanchev (added)
Comment:
You should run migrate after each squash:
> 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.
Do you think this needs to be clearer in the
[https://docs.djangoproject.com/en/dev/topics/migrations/#migration-
squashing docs]?
--
Ticket URL: <https://code.djangoproject.com/ticket/36141#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/01070194a6c432d9-1b0174d9-bc04-4cba-8385-07a6d2520636-000000%40eu-central-1.amazonses.com.
