#34993: Unexpected behaviour when filtering across mult-value (aka tomany) 
joins.
-------------------------------------+-------------------------------------
     Reporter:  Gordon Wrigley       |                    Owner:  nobody
         Type:  Uncategorized        |                   Status:  closed
    Component:  Database layer       |                  Version:  4.1
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:  duplicate
     Keywords:                       |             Triage Stage:
                                     |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by Gordon Wrigley):

 Could you direct me to that documention? Are you referring to the second
 note here https://docs.djangoproject.com/en/4.2/topics/db/queries
 /#spanning-multi-valued-relationships

 Should my mental model be "always use subqueries when I want two fields
 off the same multi value relation"?

 You didn't address the deeply nested and redundant inner query behaviour,
 would you like me to reraise that somewhere else?

-- 
Ticket URL: <https://code.djangoproject.com/ticket/34993#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 unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018bfc01fc57-a0cb929f-6798-48c1-87d4-e68866ddc1f4-000000%40eu-central-1.amazonses.com.

Reply via email to