p15693087
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

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
This commit is contained in:
Russell Keith-Magee 2010-05-10 13:14:19 +00:00
parent fa2062d1db
commit b34edc76eb
3 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/ref/models/querysets.txt
View File

@ -92,7 +92,7 @@ time, defeating the purpose of caching). This means that when you unpickle a
than the results that are currently in the database. than the results that are currently in the database.
If you only want to pickle the necessary information to recreate the If you only want to pickle the necessary information to recreate the
``Queryset`` from the database at a later time, pickle the ``query`` attribute ``QuerySet`` from the database at a later time, pickle the ``query`` attribute
of the ``QuerySet``. You can then recreate the original ``QuerySet`` (without of the ``QuerySet``. You can then recreate the original ``QuerySet`` (without
any results loaded) using some code like this:: any results loaded) using some code like this::

4
docs/topics/db/aggregation.txt
View File

@ -96,7 +96,7 @@ Generating aggregates for each item in a QuerySet
================================================= =================================================
The second way to generate summary values is to generate an independent The second way to generate summary values is to generate an independent
summary for each object in a ``Queryset``. For example, if you are retrieving summary for each object in a ``QuerySet``. For example, if you are retrieving
a list of books, you may want to know how many authors contributed to a list of books, you may want to know how many authors contributed to
each book. Each Book has a many-to-many relationship with the Author; we each book. Each Book has a many-to-many relationship with the Author; we
want to summarize this relationship for each book in the ``QuerySet``. 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::
Ordinarily, annotations are generated on a per-object basis - an annotated Ordinarily, annotations are generated on a per-object basis - an annotated
``QuerySet`` will return one result for each object in the original ``QuerySet`` will return one result for each object in the original
``Queryset``. However, when a ``values()`` clause is used to constrain the ``QuerySet``. However, when a ``values()`` clause is used to constrain the
columns that are returned in the result set, the method for evaluating columns that are returned in the result set, the method for evaluating
annotations is slightly different. Instead of returning an annotated result annotations is slightly different. Instead of returning an annotated result
for each result in the original ``QuerySet``, the original results are for each result in the original ``QuerySet``, the original results are

2
docs/topics/db/models.txt
View File

@ -1081,7 +1081,7 @@ attribute when you use the proxy. This is easy::
Now normal ``User`` queries will be unorderd and ``OrderedUser`` queries will Now normal ``User`` queries will be unorderd and ``OrderedUser`` queries will
be ordered by ``username``. be ordered by ``username``.
Querysets still return the model that was requested QuerySets still return the model that was requested
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
There is no way to have Django return, say, a ``MyUser`` object whenever you There is no way to have Django return, say, a ``MyUser`` object whenever you