#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
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => duplicate
Comment:
This was discussed many times, e.g. #27936. It's recommended and
documented to use subqueries in such cases. In the future, start by asking
questions on support channels before creating a ticket.
> AFAIK the docs don't say anything either way on what this should do.
Docs cannot describe every possible configuration, `exclude(filters)`
works as `exclude(Q(filters))`.
--
Ticket URL: <https://code.djangoproject.com/ticket/34993#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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018bfbddd3b3-e9b07054-aed1-4bef-99b2-d7e17b4657df-000000%40eu-central-1.amazonses.com.
