Thank you all for the replies. @Josh Smeaton Essentially yes; specifically I was wondering whether I was failing to consider behaviour that couldn't be modeled via a Q object, since as you mention the current https://docs.djangoproject.com/en/2.0/topics/db/queries/#spanning-multi-valued-relationships documentation uses AND vs OR to justify the behaviour.
@Marten Kenbeek Got it. Thank you sincerely for the example. I feel a bit foolish now it's clicked as I realize the documentation says nearly the same thing, but for some reason even after reading through the spanning multi-valued relationship documentation multiple times I was completely missing the point. So would I be correct in stating that all the reported weirdness with objects appearing multiple times in QuerySets is mostly a side effect of implementing the AND condition on *any* related objects? -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/95015709-2809-4895-97e6-21d02b49f803%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
