#27903: RenameModel does not not change ForeignKey with related_name='+'
-------------------------------------+-------------------------------------
Reporter: Alexander Schrijver | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.10
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* component: Uncategorized => Migrations
Comment:
I assume this was fixed by the `RenameModel` refactor in #27310 as we
don't rely on ''related objects'' anymore (which can be missing when
`related_name` ends with `'+'`).
I'm not sure this is worth fixing at this point in the 1.10 release cycle.
--
Ticket URL: <https://code.djangoproject.com/ticket/27903#comment:2>
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/065.16da7e21a604eca92f58ddcea88c1832%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
