#23622: Subquery doesn't respect order when not bound to a __pk__ field.
-------------------------------------+-------------------------------------
Reporter: ris | Owner:
Type: Bug | Status: new
Component: Database layer | Version: 1.7
(models, ORM) |
Severity: Normal | Resolution:
Keywords: subquery order | Triage Stage: Accepted
distinct |
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:"baa732ac9f18b6ed0ca386c632e15c9fb3037e39" baa732a]:
{{{
#!CommitTicketReference repository=""
revision="baa732ac9f18b6ed0ca386c632e15c9fb3037e39"
Refs #23622 -- Added tests to ensure ordering is retained for distinct on
fields subqueries.
The ticket was already fixed by
b68212f539f206679580afbfd008e7d329c9cd31.
Thanks to Beauhurst for commissioning the work on this ticket.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/23622#comment:4>
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/061.631e529979c609efd75968e5fd45c7e1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
