#24225: KeyError when migrating in 1.8a1/master@728b6fd (does not occur in
1.7.3)
---------------------------------+-------------------------------------
Reporter: hheimbuerger | Owner: MarkusH
Type: Bug | Status: assigned
Component: Migrations | Version: 1.8alpha1
Severity: Release blocker | 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 Markus Holtermann <info@…>):
In [changeset:"58d0dd9260156067263ea7a2da2685c3cd88e18a"]:
{{{
#!CommitTicketReference repository=""
revision="58d0dd9260156067263ea7a2da2685c3cd88e18a"
Refs #24225 -- Added failing test case for removing a previously added
field in migrations
When a related field is deleted, the related model must be updated. As
unchanged models are shared in migration states, the related model must
be re-rendered so that the change applies to a new copy of the related
model.
Thanks Henrik Heimbuerger for the report.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24225#comment:14>
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.a13ff4bd741726e9a1ee1a79f842d133%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
