#24225: KeyError when migrating in 1.8a1/master@728b6fd (does not occur in
1.7.3)
---------------------------------+-------------------------------------
Reporter: hheimbuerger | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.8alpha1
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+-------------------------------------
Comment (by hheimbuerger):
Unfortunately, I don't. I extracted the suspected issue I described above
into a new project, but that works fine. So there must be one more factor
I'm missing to trigger the issue. Really reducing my actual big project
down to the cause would take me days, which I unfortunately don't have.
Besides, I wouldn't even know where to start.
I still can attach the debugger, so if you can tell me where to start
inspecting the state at the point in time the exception was raised, I can
do that.
Other than that, I now just removed those two aforementioned `AddField`
and `RemoveField` instructions from my old migrations (they are really
old, the two very first migrations—so while I'm sure editing old
migrations by hand is not a best practice, it shouldn't break anything in
this case) and that fixed it for my app.
So feel free to close as 'cannot reproduce'.
--
Ticket URL: <https://code.djangoproject.com/ticket/24225#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 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/070.425b10a4a25e12bb43b3e74290380aff%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
