From 4531ded061831a9cf402c6c5d84e42f31bc025ad Mon Sep 17 00:00:00 2001
From: Kevin Stone <kevinastone@gmail.com>
Date: Thu, 28 Mar 2013 18:48:48 -0700
Subject: [PATCH] Removed pagination regression special case for Django<1.4.
Having DjangoFilterBackend return an actual query set fixes this issue.
Signed-off-by: Kevin Stone <kevinastone@gmail.com>
---
rest_framework/tests/pagination.py | 10 ----------
1 file changed, 10 deletions(-)
diff --git a/rest_framework/tests/pagination.py b/rest_framework/tests/pagination.py
index d2c9b0513..6b8ef02f0 100644
--- a/rest_framework/tests/pagination.py
+++ b/rest_framework/tests/pagination.py
@@ -129,16 +129,6 @@ class IntegrationTestPaginationAndFiltering(TestCase):
view = FilterFieldsRootView.as_view()
EXPECTED_NUM_QUERIES = 2
- if django.VERSION < (1, 4):
- # On Django 1.3 we need to use django-filter 0.5.4
- #
- # The filter objects there don't expose a `.count()` method,
- # which means we only make a single query *but* it's a single
- # query across *all* of the queryset, instead of a COUNT and then
- # a SELECT with a LIMIT.
- #
- # Although this is fewer queries, it's actually a regression.
- EXPECTED_NUM_QUERIES = 1
request = factory.get('/?decimal=15.20')
with self.assertNumQueries(EXPECTED_NUM_QUERIES):