#24254: Queries using distinct() and order_by() cannot be used with the __in
lookup
-------------------------------------+-------------------------------------
Reporter: Torsten Bronger | Owner: Simon
| Charette
Type: Bug | Status: closed
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"71da2b4f11938532df63817f8ea01e30c0875a05" 71da2b4f]:
{{{
#!CommitTicketReference repository=""
revision="71da2b4f11938532df63817f8ea01e30c0875a05"
[2.0.x] Refs #24254 -- Removed unnecessary SQL AS clause in
SQLCompiler.as_sql().
Incorrect on Oracle.
Backport of 11ade8eefd32f5bc7ee6379b77824f02ca61c20b from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24254#comment:13>
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/065.676ae321c22c316b77c2c0ffccb5722b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
