#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
-------------------------------------+-------------------------------------
Comment (by Claude Paroz <claude@…>):
In [changeset:"70ff455a35066a1b6e2db03f211f56c7b38285eb" 70ff455]:
{{{
#!CommitTicketReference repository=""
revision="70ff455a35066a1b6e2db03f211f56c7b38285eb"
[1.8.x] 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.
Backport of fb5c7748da from master.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24615#comment:12>
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.0b449d7d722c19d3f94144495ff23f3b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
