#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
-------------------------------+------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"d0607a7eee75121527cd03c89de82a222e298eae" d0607a7e]:
{{{
#!CommitTicketReference repository=""
revision="d0607a7eee75121527cd03c89de82a222e298eae"
[1.7.x] Fixed #24354 -- Prevented repointing of relations on superclasses
when migrating a subclass's name change
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24354#comment:9>
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/071.37a7666d4cf23df3da233031a7070a2b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
