#24354: Migrations that rename subclasses cause problems with relations
-------------------------------+--------------------------------------
Reporter: MatthewWilkes | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.7
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by MatthewWilkes):
I'm sorry, are you asking me to bisect the current state or saying though
found that commit from bisecting?
Either way, that's right. That PR fixes the issue and it was present on
master immediately prior to it being merged. I know this because that's
where I originally fixed it, and had to change my PR to target 1.7 as
MarkusH's PR landed while I was working in it.
He advised that the changes on 1.8 would not be back ported to the 1.7
line.
--
Ticket URL: <https://code.djangoproject.com/ticket/24354#comment:4>
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.4e5b6649e4f406e3a2128b757d61e1e7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
