#29458: Documentation incorrectly says Model._meta.get_field() uses related_name
instead of related_query_name
-------------------------------+------------------------------------
Reporter: Tomasz Knapik | Owner: Jeff
Type: Bug | Status: closed
Component: Documentation | Version: 2.1
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"ddd9272c2e323b4e8937774425ee93ebebf8eeba" ddd9272c]:
{{{
#!CommitTicketReference repository=""
revision="ddd9272c2e323b4e8937774425ee93ebebf8eeba"
[2.1.x] Fixed #29458 -- Doc'd how related_query_name affects
Model._meta.get_field().
Backport of 2d6776ffe0b58f729f4372635b49a59da99ca206 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/29458#comment:7>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.26d2d5dd0f491f5da015e45372eb2657%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
