#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
-------------------------------------+-------------------------------------
Changes (by Simon Charette <charette.s@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"4acae21846f6212aa992763e587c7e201828d7b0" 4acae218]:
{{{
#!CommitTicketReference repository=""
revision="4acae21846f6212aa992763e587c7e201828d7b0"
Fixed #24254 -- Fixed queries using the __in lookup with querysets using
distinct() and order_by().
Thanks Tim for the review.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24254#comment:11>
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.e5ba814d9ae14f7180941c3cb227f59e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
