#20939: Convert QuerySet to Query when filtering
-------------------------------------+-------------------------------------
Reporter: Anssi Kääriäinen | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"eb4724a0632928bda2a512a9117a91260096e457" eb4724a0]:
{{{
#!CommitTicketReference repository=""
revision="eb4724a0632928bda2a512a9117a91260096e457"
Reverted "Refs #20939 -- Moved subquery ordering clearing optimization to
the __in lookup."
This reverts commit e62ea0bb9cbb54c1eef848871fe3eab2bad268dc since it
broke multi-column __in lookups and _meta.order_wrt on Oracle.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/20939#comment:6>
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/066.5ae721a029e985865c3c10ae4cdd9aa9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
