#33734: InconsistentMigrationHistory triggers on squashed migrations when not
all
replaced migrations are applied
-------------------------------------+-------------------------------------
Reporter: GwynBleidD | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 3.2
Severity: Normal | Resolution: needsinfo
Keywords: migrations squash | Triage Stage:
inconsistentmigrationhistory | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => needsinfo
Comment:
I cannot reproduce any `InconsistentMigrationHistory` when only `A.0001`
and `B.0001` are applied (`B.0002` from the ticket description doesn't
exist.)
--
Ticket URL: <https://code.djangoproject.com/ticket/33734#comment:2>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/01070180f0590903-c3e345cd-a623-4e50-9aea-ca8a6c90b873-000000%40eu-central-1.amazonses.com.
