summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorAymeric Augustin <aymeric.augustin@m4x.org>2012-01-21 15:32:52 +0000
committerAymeric Augustin <aymeric.augustin@m4x.org>2012-01-21 15:32:52 +0000
commitf0d467675040dbb979015d97adba449dc7fd02ad (patch)
tree211cbbb970e6bf59092729551dba798c984e25a4 /docs
parent905e33f84a1a10e4f0183d879c52076ef876fc3b (diff)
Fixed #10139 -- Clarified that slicing an evaluated QuerySet returns a list, not a QuerySet. Thanks ori for the patch.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@17383 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs')
-rw-r--r--docs/ref/models/querysets.txt9
1 files changed, 5 insertions, 4 deletions
diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt
index 76335550ae..103cae1240 100644
--- a/docs/ref/models/querysets.txt
+++ b/docs/ref/models/querysets.txt
@@ -32,10 +32,11 @@ You can evaluate a ``QuerySet`` in the following ways:
print e.headline
* **Slicing.** As explained in :ref:`limiting-querysets`, a ``QuerySet`` can
- be sliced, using Python's array-slicing syntax. Usually slicing a
- ``QuerySet`` returns another (unevaluated) ``QuerySet``, but Django will
- execute the database query if you use the "step" parameter of slice
- syntax.
+ be sliced, using Python's array-slicing syntax. Slicing an unevaluated
+ ``QuerySet`` usually returns another unevaluated ``QuerySet``, but Django
+ will execute the database query if you use the "step" parameter of slice
+ syntax, and will return a list. Slicing a ``QuerySet`` that has been
+ evaluated (partially or fully) also returns a list.
* **Pickling/Caching.** See the following section for details of what
is involved when `pickling QuerySets`_. The important thing for the