#24615: ordering by expression not part of SELECT is broken
-------------------------------------+-------------------------------------
Reporter: MattBlack85 | Owner: nobody
Type: Bug | Status: closed
Component: GIS | Version: 1.8
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Claude Paroz <claude@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"fb5c7748daa25a40bfc62834acb5731c71a6b713" fb5c7748]:
{{{
#!CommitTicketReference repository=""
revision="fb5c7748daa25a40bfc62834acb5731c71a6b713"
Fixed #24615 -- ordering by expression not part of SELECT
Fixed queries where an expression was used in order_by() but the
expression wasn't in the query's select clause (for example the
expression could be masked by .values() call)
Thanks to Trac alias MattBlack85 for the report.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24615#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/069.77e72ac562df2cd9ccd629160cb76569%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
