#7070: Query.get_ordering doesn't support foreign key related ordering when
combined with distinct()
-----------------------------+---------------------------------------------
Reporter: matt@… | Owner: nobody
Type: | Status: closed
Component: Uncategorized | Version: queryset-refactor
Severity: | Resolution: fixed
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
-----------------------------+---------------------------------------------
Changes (by Tim Graham <timograham@…>):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
In [changeset:"c754bdc45bdcd9b2a03d4e3e10ea2a742456de91" c754bdc]:
{{{
#!CommitTicketReference repository=""
revision="c754bdc45bdcd9b2a03d4e3e10ea2a742456de91"
Refs #7070 -- Improved test for extra(), values(), distinct() and
ordering() all together.
Tested that the extra select that appears in the select clause only
because of
distinct() and order_by() doesn't appear in the result values.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/7070#comment:2>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/073.8e4c2829ac819270f45dde418b9995b3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
