#24900: KeyError when trying to migrate to a replaced migration
----------------------------+------------------------------------
Reporter: carljm | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.8
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 shaib):
* cc: shaib (added)
Comment:
Just ran into this. FWIW, workaround, as long as we do '''not''' do what
comment:5:ticket:24902 recommends (which is to keep the state of squashed
migrations in the db), is to simply move the squashed migration file away,
migrate backwards to your heart's content, then bring it back.
--
Ticket URL: <https://code.djangoproject.com/ticket/24900#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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.74f9295219beb37e11f6d512672ec2d9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
