#31591: Spanning relationship backwards when related_name is used.
-------------------------------------+-------------------------------------
     Reporter:  Nat S Dunn           |                    Owner:  Carlton
         Type:                       |  Gibson
  Cleanup/optimization               |                   Status:  closed
    Component:  Documentation        |                  Version:  3.0
     Severity:  Normal               |               Resolution:  fixed
     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
-------------------------------------+-------------------------------------

Comment (by Mariusz Felisiak <felisiak.mariusz@…>):

 In [changeset:"844e0591f9591854a0411fb8d90282737f17c40c" 844e0591]:
 {{{
 #!CommitTicketReference repository=""
 revision="844e0591f9591854a0411fb8d90282737f17c40c"
 [3.1.x] Fixed #31591 -- Clarified "reverse" lookup name in making queries
 docs.

 Backport of 5af17babb0f895cf129fdeee92548d2ac12e78e2 from master
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/31591#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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.80bb95f8bf785d163faf974cf4a19c12%40djangoproject.com.

Reply via email to