#24354: Migrations that rename subclasses cause problems with relations
-------------------------------+------------------------------------
Reporter: MatthewWilkes | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 1.7
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------+------------------------------------
Comment (by Markus Holtermann <info@…>):
In [changeset:"e4b7daec11c3849f5dae46ddfad5fe9ef03c2482" e4b7daec]:
{{{
#!CommitTicketReference repository=""
revision="e4b7daec11c3849f5dae46ddfad5fe9ef03c2482"
Refs #24354 -- Prevented repointing of relations on superclasses when
migrating a subclass's name change
The issue was hidden on 1.8+ until #24573 due to a bug inside the model
reloading process.
Forwardport of patch from ae87ad005f7b62f5fa5a29ef07443fa1bbb9baf0
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24354#comment:12>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/071.29d2b2a2b85cf2d16826d3258b2c73dd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
