Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

[1.1.X] Fixed #12678 -- Corrected a few references to Queryset into Q…

…uerySet. Thanks to ChrisMorgan for the report, and timo for the patch.

Backport of r13211 from trunk.

git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.1.X@13216 bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
commit b7b0ebb3adf89b7abf8a66551077b6d110700ed6 1 parent 5627b26
Russell Keith-Magee authored May 10, 2010
2  docs/ref/models/querysets.txt
@@ -88,7 +88,7 @@ time, defeating the purpose of caching). This means that when you unpickle a
88 88
 than the results that are currently in the database.
89 89
 
90 90
 If you only want to pickle the necessary information to recreate the
91  
-``Queryset`` from the database at a later time, pickle the ``query`` attribute
  91
+``QuerySet`` from the database at a later time, pickle the ``query`` attribute
92 92
 of the ``QuerySet``. You can then recreate the original ``QuerySet`` (without
93 93
 any results loaded) using some code like this::
94 94
 
4  docs/topics/db/aggregation.txt
@@ -96,7 +96,7 @@ Generating aggregates for each item in a QuerySet
96 96
 =================================================
97 97
 
98 98
 The second way to generate summary values is to generate an independent
99  
-summary for each object in a ``Queryset``. For example, if you are retrieving
  99
+summary for each object in a ``QuerySet``. For example, if you are retrieving
100 100
 a list of books, you may want to know how many authors contributed to
101 101
 each book. Each Book has a many-to-many relationship with the Author; we
102 102
 want to summarize this relationship for each book in the ``QuerySet``.
@@ -257,7 +257,7 @@ that have contributed to the book, you could use the following query::
257 257
 
258 258
 Ordinarily, annotations are generated on a per-object basis - an annotated
259 259
 ``QuerySet`` will return one result for each object in the original
260  
-``Queryset``. However, when a ``values()`` clause is used to constrain the
  260
+``QuerySet``. However, when a ``values()`` clause is used to constrain the
261 261
 columns that are returned in the result set, the method for evaluating
262 262
 annotations is slightly different. Instead of returning an annotated result
263 263
 for each result in the original ``QuerySet``, the original results are
2  docs/topics/db/models.txt
@@ -1062,7 +1062,7 @@ attribute when you use the proxy. This is easy::
1062 1062
 Now normal ``User`` queries will be unorderd and ``OrderedUser`` queries will
1063 1063
 be ordered by ``username``.
1064 1064
 
1065  
-Querysets still return the model that was requested
  1065
+QuerySets still return the model that was requested
1066 1066
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1067 1067
 
1068 1068
 There is no way to have Django return, say, a ``MyUser`` object whenever you

0 notes on commit b7b0ebb

Please sign in to comment.
Something went wrong with that request. Please try again.