#36166: Backwards migration to replaced migration leads to
InconsistentMigrationHistory on forward migrate
------------------------------------+------------------------------------
Reporter: Klaas van Schelven | Owner: (none)
Type: Bug | Status: new
Component: Migrations | Version: 5.1
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------------+------------------------------------
Comment (by HarshAlreja):
I have verified the patch provided in PR #20490. I wrote a reproduction
script that simulates the migration squash and rollback scenario.
On main: The bug was reproducible (Migration 0003 remained applied after
rollback).
With PR #20490: The bug is fixed (Migration 0003 was correctly unapplied).
Verified on Windows/SQLite. The patch works as expected.
--
Ticket URL: <https://code.djangoproject.com/ticket/36166#comment:6>
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/0107019ba3f1f813-2faf7a2f-cbd1-4347-a4be-654acf753cc2-000000%40eu-central-1.amazonses.com.
