Changes between Initial Version and Version 1 of Ticket #31591, comment 1


Ignore:
Timestamp:
May 19, 2020, 8:53:54 AM (5 years ago)
Author:
Carlton Gibson

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #31591, comment 1

    initial v1  
    11OK, yes. Good spot.
    22
    3 The docs should probably cross-reference https://docs.djangoproject.com/en/3.0/topics/db/queries/#following-relationships-backward here.
     3The docs should probably cross-reference ~~https://docs.djangoproject.com/en/3.0/topics/db/queries/#following-relationships-backward~~ `related_query_name` here.
    44
    5 At the least it's lowercased + `_set`, so correcting the examples to match the sample models at the top would probably also ease confusion.
     5~~At the least it's lowercased + `_set`, so correcting the examples to match the sample models at the top would probably also ease confusion.~~
    66
    77[https://github.com/django/django/pull/12935 PR]
     8
     9**Update**: It's the lookup, rather than the reverse descriptor that's in play here so it's `related_query_name`  that's really in play.
     10
     11> ...unless you have used related_name to override the name of the relationship, in which case you should use the related_name you have set,
     12
     13...**unless you set related_query_name**... — and so on. I'm inclined towards just adding a , "By default, ... " 🤔
     14
Back to Top