From d00c013cc8477de9a75e4b4f5806034549e5a5e1 Mon Sep 17 00:00:00 2001 From: Malcolm Tredinnick Date: Thu, 8 Jan 2009 05:15:41 +0000 Subject: [PATCH] Remove any ordering from a nested select query (in the where-clause). This fixes r9701 for Oracle (the test introduced there did its job and failed previously). git-svn-id: http://code.djangoproject.com/svn/django/trunk@9714 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- django/db/models/sql/query.py | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/django/db/models/sql/query.py b/django/db/models/sql/query.py index 432e5e6332..876099cb1f 100644 --- a/django/db/models/sql/query.py +++ b/django/db/models/sql/query.py @@ -317,11 +317,13 @@ class BaseQuery(object): """ Perform the same functionality as the as_sql() method, returning an SQL string and parameters. However, the alias prefixes are bumped - beforehand (in a copy -- the current query isn't changed). + beforehand (in a copy -- the current query isn't changed) and any + ordering is removed. Used when nesting this query inside another. """ obj = self.clone() + obj.clear_ordering(True) obj.bump_prefix() return obj.as_sql()