#24386: Querysets with filters and exclusions based on deep relations build
invalid
queries
-------------------------------------+-------------------------------------
Reporter: rtpg | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by shaib):
* needs_better_patch: => 0
* stage: Unreviewed => Accepted
* needs_tests: => 1
* needs_docs: => 0
Comment:
Accepting based on details in report, didn't reproduce myself.
Just wanted to note for the submitter that even without the bug, the query
you wrote would not achieve the stated goals -- it would return no
employees. To do what you intended, you need to replace your `lte` with
`lt`. Also, another approach for this relies on annotations (annotate
employee with `Min(owner__employee__startdate)` and filter on that).
--
Ticket URL: <https://code.djangoproject.com/ticket/24386#comment:1>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/062.20374addadd8c3490f4ab212207843a3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
