From fb5c7748daa25a40bfc62834acb5731c71a6b713 Mon Sep 17 00:00:00 2001 From: Anssi Kääriäinen Date: Wed, 15 Apr 2015 08:46:19 +0300 Subject: 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. --- docs/releases/1.8.1.txt | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'docs') diff --git a/docs/releases/1.8.1.txt b/docs/releases/1.8.1.txt index fd2140bbf0..976179c41e 100644 --- a/docs/releases/1.8.1.txt +++ b/docs/releases/1.8.1.txt @@ -49,3 +49,7 @@ Bugfixes remove usage of referencing views by dotted path in :func:`~django.conf.urls.url` which is deprecated in Django 1.8 (:ticket:`24635`). + +* Fixed queries where an expression was referenced in ``order_by()``, but wasn't + part of the select clause. An example query is + ``qs.annotate(foo=F('field')).values('pk').order_by('foo'))`` (:ticket:`24615`). -- cgit v1.3