#32983: Prevent developers from defining a related_name on symmetrical
ManyToManyFields
-------------------------------------+-------------------------------------
Reporter: Nick Touran | Owner: Nick
Type: | Touran
Cleanup/optimization | Status: assigned
Component: Database layer | Version: 4.0
(models, ORM) |
Severity: Normal | Resolution:
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 Carlton Gibson):
* needs_better_patch: 0 => 1
* stage: Unreviewed => Accepted
Comment:
OK, I guess we can do something here — it probably is a source of
confusion.
The same issue was raised in #18021 (but as an invalid bug report, rather
than suggesting improving the messaging).
Looking at the PR — I'm sceptical about just raising an error — this will
likely break code in the wild.
Can we investigate adding a system check here instead?
There are several similar checks for related fields already:
https://docs.djangoproject.com/en/3.2/ref/checks/#related-fields
--
Ticket URL: <https://code.djangoproject.com/ticket/32983#comment:3>
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.71cb929902c88c04c5937f51a1c19093%40djangoproject.com.
