#10913: Default related_name is broken
-------------------------------------+-------------------------------------
Reporter: neithere | Owner: nobody
Type: | Status: reopened
Cleanup/optimization | Component: Documentation
Milestone: | Severity: Normal
Version: SVN | Keywords: orm, related_name,
Resolution: | Has patch: 0
Triage Stage: Accepted | Needs tests: 0
Needs documentation: 1 | Easy pickings: 0
Patch needs improvement: 0 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
Changes (by russellm):
* needs_docs: 0 => 1
* type: Uncategorized => Cleanup/optimization
* component: Database layer (models, ORM) => Documentation
* stage: Unreviewed => Accepted
Comment:
The code example you provide is working as intended. However, I'll accept
this ticket as a documentation issue; a quick scan of the related_name
docs didn't reveal anything describing this behavior.
--
Ticket URL: <https://code.djangoproject.com/ticket/10913#comment:4>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
