From 016f12a2c27fd6006d43cc32af734dfd0ea96f98 Mon Sep 17 00:00:00 2001 From: Malcolm Tredinnick Date: Sun, 1 Mar 2009 01:59:18 +0000 Subject: [1.0.X] Fixed insert/update handling when no database interaction is required. Fixed #10205 as part of this. Backport of r9926 from trunk. git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.0.X@9927 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- tests/regressiontests/queries/models.py | 14 ++++++++++++++ 1 file changed, 14 insertions(+) (limited to 'tests') diff --git a/tests/regressiontests/queries/models.py b/tests/regressiontests/queries/models.py index 755b9ffc3f..e3aebd7915 100644 --- a/tests/regressiontests/queries/models.py +++ b/tests/regressiontests/queries/models.py @@ -1056,6 +1056,20 @@ cases). Bug #9985 -- qs.values_list(...).values(...) combinations should work. >>> Note.objects.values_list("note", flat=True).values("id").order_by("id") [{'id': 1}, {'id': 2}, {'id': 3}] +>>> Annotation.objects.filter(notes__in=Note.objects.filter(note="n1").values_list('note').values('id')) +[] + +Bug #10028 -- ordering by model related to nullable relations(!) should use +outer joins, so that all results are included. +>>> _ = Plaything.objects.create(name="p1") +>>> Plaything.objects.all() +[] + +Bug #10205 -- When bailing out early because of an empty "__in" filter, we need +to set things up correctly internally so that subqueries can continue properly. +>>> Tag.objects.filter(name__in=()).update(name="foo") +0 + """} # In Python 2.3 and the Python 2.6 beta releases, exceptions raised in __len__ -- cgit v1.3