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

Corrected explanation of values() and extra() interaction in querysets. 

Fixes #15546, refs #13455. The original documentation patch
inadvertently muddied the waters in one aspect and this commit tidies
that up.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@16697 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Malcolm Tredinnick 2011-08-26 21:13:01 +00:00
parent e0ae9db272
commit a4a250a296
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -436,11 +436,11 @@ A few subtleties that are worth mentioning:
ordering can affect the results. See the note in :meth:`distinct` for ordering can affect the results. See the note in :meth:`distinct` for
details. details.
* If you use a ``values()`` clause after an ``extra()`` clause, * If you use a ``values()`` clause after an :py:meth:`extra()` call,
any fields defined by a ``select`` argument in the ``extra()`` any fields defined by a ``select`` argument in the :py:meth:`extra()`
must be explicitly included in the ``values()`` clause. However, must be explicitly included in the ``values()`` call. Any
if the ``extra()`` clause is used after the ``values()``, the :py:meth:`extra()` call made after a ``values()`` call with have its
fields added by the select will be included automatically. extra selected fields ignored.
A ``ValuesQuerySet`` is useful when you know you're only going to need values A ``ValuesQuerySet`` is useful when you know you're only going to need values
from a small number of the available fields and you won't need the from a small number of the available fields and you won't need the