#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: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------------+------------------------------------
Changes (by Sarah Boyce):
* cc: Jacob Walls (added)
Comment:
> Not in my world (Django 5.1):
Ah apologies, I had ran `python manage.py squashmigrations squashme 0001
0002` which had the different name. Replicated
> I'm not sure that line of reasoning matters much to the present
discussion
I was thinking that there were additional manual steps here (which I
believe would be relevant as it would reduce the likelihood of someone
encountering the error), but the commands being ran to create the
migration were different.
cc-ing Jacob as he was involved in that PR
--
Ticket URL: <https://code.djangoproject.com/ticket/36166#comment:3>
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/01070194d0380c87-1f08d987-6fd8-48a4-9008-44c6f72e175a-000000%40eu-central-1.amazonses.com.
