Skip to content

Commit b34edc7

Browse files
committed
Fixed #12678 -- Corrected a few references to Queryset into QuerySet. Thanks to ChrisMorgan for the report, and timo for the patch.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@13211 bcc190cf-cafb-0310-a4f2-bffc1f526a37
1 parent fa2062d commit b34edc7

File tree

3 files changed

+4
-4
lines changed

3 files changed

+4
-4
lines changed

docs/ref/models/querysets.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -92,7 +92,7 @@ time, defeating the purpose of caching). This means that when you unpickle a
9292
than the results that are currently in the database.
9393

9494
If you only want to pickle the necessary information to recreate the
95-
``Queryset`` from the database at a later time, pickle the ``query`` attribute
95+
``QuerySet`` from the database at a later time, pickle the ``query`` attribute
9696
of the ``QuerySet``. You can then recreate the original ``QuerySet`` (without
9797
any results loaded) using some code like this::
9898

docs/topics/db/aggregation.txt

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -96,7 +96,7 @@ Generating aggregates for each item in a QuerySet
9696
=================================================
9797

9898
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
100100
a list of books, you may want to know how many authors contributed to
101101
each book. Each Book has a many-to-many relationship with the Author; we
102102
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::
257257

258258
Ordinarily, annotations are generated on a per-object basis - an annotated
259259
``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
261261
columns that are returned in the result set, the method for evaluating
262262
annotations is slightly different. Instead of returning an annotated result
263263
for each result in the original ``QuerySet``, the original results are

docs/topics/db/models.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1081,7 +1081,7 @@ attribute when you use the proxy. This is easy::
10811081
Now normal ``User`` queries will be unorderd and ``OrderedUser`` queries will
10821082
be ordered by ``username``.
10831083

1084-
Querysets still return the model that was requested
1084+
QuerySets still return the model that was requested
10851085
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
10861086

10871087
There is no way to have Django return, say, a ``MyUser`` object whenever you

0 commit comments

Comments
 (0)