From 3b5d975ff67cfeebc4ec8f49b7a851aa3b7401e9 Mon Sep 17 00:00:00 2001 From: Malcolm Tredinnick Date: Fri, 24 Oct 2008 06:24:04 +0000 Subject: [PATCH] Fixed #9411 -- Changed the test from r9081 to be more robust across different database backends. git-svn-id: http://code.djangoproject.com/svn/django/trunk@9254 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- tests/regressiontests/queries/models.py | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/tests/regressiontests/queries/models.py b/tests/regressiontests/queries/models.py index f3831df5b6a..0eda8f02da5 100644 --- a/tests/regressiontests/queries/models.py +++ b/tests/regressiontests/queries/models.py @@ -974,11 +974,12 @@ about them and shouldn't do bad things. >>> expected == result True -Make sure bump_prefix() (an internal Query method) doesn't (re-)break. ->>> query = Tag.objects.values_list('id').order_by().query ->>> query.bump_prefix() ->>> print query.as_sql()[0] -SELECT U0."id" FROM "queries_tag" U0 +Make sure bump_prefix() (an internal Query method) doesn't (re-)break. It's +sufficient that this query runs without error. +>>> qs = Tag.objects.values_list('id', flat=True).order_by('id') +>>> qs.query.bump_prefix() +>>> list(qs) +[1, 2, 3, 4, 5] Calling order_by() with no parameters removes any existing ordering on the model. But it should still be possible to add new ordering after that.