#31591: Spanning relationship backwards when related_name is used.
-------------------------------------+-------------------------------------
Reporter: Nat S Dunn | Owner: Carlton
Type: | Gibson
Cleanup/optimization | Status: assigned
Component: Documentation | Version: 3.0
Severity: Normal | Resolution:
Keywords: related_name | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* owner: nobody => Carlton Gibson
* status: new => assigned
* has_patch: 0 => 1
* stage: Unreviewed => Accepted
Comment:
OK, yes. Good spot.
The docs should probably cross-reference
https://docs.djangoproject.com/en/3.0/topics/db/queries/#following-
relationships-backward here.
At the least it's lowercased + `_set`, so correcting the examples to match
the sample models at the top would probably also ease confusion.
[https://github.com/django/django/pull/12935 PR]
--
Ticket URL: <https://code.djangoproject.com/ticket/31591#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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.b7b9d9dbb1d7b05f0717c48392ec0991%40djangoproject.com.
