[1.2.X] Fixed #14366 -- Model.objects.none().values() now correctly returns a QuerySet with no items, rather than raising an Exception. Thanks to Carl Meyer for the patch. Backport of [14084].

git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.2.X@14085 bcc190cf-cafb-0310-a4f2-bffc1f526a37

1 files changed, 7 insertions, 1 deletions

diff --git a/tests/regressiontests/queries/tests.py b/tests/regressiontests/queries/tests.py
index 03c28b06a7..75653fc660 100644
--- a/tests/regressiontests/queries/tests.py
+++ b/tests/regressiontests/queries/tests.py
@@ -4,7 +4,7 @@ from django.db import DatabaseError, connections, DEFAULT_DB_ALIAS
 from django.db.models import Count
 from django.test import TestCase
 
-from models import Tag, Annotation, DumbCategory, Note, ExtraInfo
+from models import Tag, Annotation, DumbCategory, Note, ExtraInfo, Number
 
 class QuerysetOrderedTests(unittest.TestCase):
     """
@@ -81,3 +81,9 @@ class CloneTests(TestCase):
             self.assertEquals(ExtraInfo.objects.filter(note__in=n_list)[0].info, 'good')
         except:
             self.fail('Query should be clonable')
+
+
+class EmptyQuerySetTests(TestCase):
+    def test_emptyqueryset_values(self):
+        "#14366 -- calling .values() on an EmptyQuerySet and then cloning that should not cause an error"
+        self.assertEqual(list(Number.objects.none().values('num').order_by('num')), [])