#27903: RenameModel does not not change ForeignKey with related_name='+'
-------------------------------------+-------------------------------------
Reporter: Alexander Schrijver | Owner: nobody
Type: Bug | Status: new
Component: Uncategorized | 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
-------------------------------------+-------------------------------------
Description changed by Alexander Schrijver:
Old description:
> When you create a ForeignKey with a related_name='+' to a second model,
> and you rename the second model, the model which is referred in the
> ForeignKey is not updated. I've created a updated
> OperationTests.test_rename_model test to show this (I'll update this
> ticket when I've created the PR). This only affects 1.10, this issue
> seems to be fixed in 1.11.
New description:
When you create a ForeignKey with a related_name='+' to a second model,
and you rename the second model, the model which is referred in the
ForeignKey is not updated. I've created a updated
OperationTests.test_rename_model test to show this (PR:
https://github.com/django/django/pull/8146). This only affects 1.10, this
issue seems to be fixed in 1.11.
--
--
Ticket URL: <https://code.djangoproject.com/ticket/27903#comment:1>
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.29b86c9249b577926751f03b4ec42eb4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
