summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFlorian Apolloner <apollo13@apolloner.eu>2012-09-16 02:45:44 -0700
committerFlorian Apolloner <apollo13@apolloner.eu>2012-09-16 02:45:44 -0700
commit935a8635c2fe5b702c18027818ef4cceda4d83cd (patch)
treed7592dc56b4c6b6ca317365caff0d7cce1231136
parente4d338ac9b0d67756cdd3437a31ed0e7e5061f59 (diff)
parent8d75b1176f280b8949aee8dc961a2acd0dacffcd (diff)
Merge pull request #372 from ptone/patch-2
Clearer wording for defer docs
-rw-r--r--docs/ref/models/querysets.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt
index 80b3158f01..8ec7cfc791 100644
--- a/docs/ref/models/querysets.txt
+++ b/docs/ref/models/querysets.txt
@@ -1050,7 +1050,7 @@ defer
In some complex data-modeling situations, your models might contain a lot of
fields, some of which could contain a lot of data (for example, text fields),
or require expensive processing to convert them to Python objects. If you are
-using the results of a queryset in some situation where you know you don't know
+using the results of a queryset in some situation where you don't know
if you need those particular fields when you initially fetch the data, you can
tell Django not to retrieve them from the database.