#24462: Using .distinct().order_by() on a queryset produces unexpected results
-------------------------------------+-------------------------------------
Reporter: trosos | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.7
(models, ORM) |
Severity: Normal | Resolution:
Keywords: distinct order_by | Triage Stage:
subquery | Unreviewed
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:"5b91802718b61346967e7991cf3585554c4c97fa" 5b91802]:
{{{
#!CommitTicketReference repository=""
revision="5b91802718b61346967e7991cf3585554c4c97fa"
[1.8.x] Refs #24462 -- Emphasized that order_by() clears previous
ordering.
Backport of b9d9ab23bdcc404708aada664e718a9d56415ca3 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24462#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/064.b94c0cab3137431f64cb46a92c46a49a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
