#36141: After double squashing migrate command fails with
InconsistentMigrationHistory
-----------------------------+--------------------------------------
Reporter: Jacob Walls | Owner: (none)
Type: Bug | Status: new
Component: Migrations | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+--------------------------------------
Changes (by Georgi Yanchev):
* has_patch: 0 => 1
* resolution: invalid =>
* status: closed => new
Comment:
I think the bug is valid, and we just hit it in our production app.
Running "migrate" after each squash is not always possible, as we can't
track all the deployments in the wild and some customers upgrade very
infrequently.
I've created a patch.
--
Ticket URL: <https://code.djangoproject.com/ticket/36141#comment:4>
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/0107019a7fa8a05a-50af5260-03e3-47ff-84b6-229858bbc0ef-000000%40eu-central-1.amazonses.com.
