#32983: Prevent developers from defining a related_name on symmetrical
ManyToManyFields
-------------------------------------+-------------------------------------
Reporter: Nick Touran | Owner: Nick
Type: | Touran
Cleanup/optimization | Status: closed
Component: Database layer | Version: 4.0
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson <carlton@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"5d4f21b16f002ed5202a68d6977346ccf53b0b0e" 5d4f21b1]:
{{{
#!CommitTicketReference repository=""
revision="5d4f21b16f002ed5202a68d6977346ccf53b0b0e"
Fixed #32983 -- Added system check for redundant related_name on
symmetrical M2M fields.
Since ManyToManyFields defined with `symmetrical=True` do not add a
related field to the target model, including a `related_name` argument
will never do what the coder likely expects. This makes including
a related_name with a symmetrical model raise a system check warning.
ticket-32983
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/32983#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/072.4d301b09a5f4ba48b34fdbcc2181a848%40djangoproject.com.
