innov
/
django1
1
0
Fork 0
Code Issues Pull Requests 1 Projects Releases Wiki Activity

Fixed #14185 - improved example SQL for 'select' example. 

Thanks to Trindaz for the suggestion.

Also fixed some references to 'lede' which is no longer part of the
example Blog model.


git-svn-id: http://code.djangoproject.com/svn/django/trunk@13652 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Luke Plant 2010-08-28 11:23:54 +00:00
parent 34740625ff
commit c00f35ae0d
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -703,9 +703,10 @@ of the arguments is required, but you should use at least one of them.
greater than Jan. 1, 2006. greater than Jan. 1, 2006.
Django inserts the given SQL snippet directly into the ``SELECT`` Django inserts the given SQL snippet directly into the ``SELECT``
statement, so the resulting SQL of the above example would be:: statement, so the resulting SQL of the above example would be something
like::
SELECT blog_entry.*, (pub_date > '2006-01-01') SELECT blog_entry.*, (pub_date > '2006-01-01') AS is_recent
FROM blog_entry; FROM blog_entry;
@ -859,7 +860,7 @@ deferred field will be retrieved from the database if you access that field
You can make multiple calls to ``defer()``. Each call adds new fields to the You can make multiple calls to ``defer()``. Each call adds new fields to the
deferred set:: deferred set::
# Defers both the body and lede fields. # Defers both the body and headline fields.
Entry.objects.defer("body").filter(rating=5).defer("headline") Entry.objects.defer("body").filter(rating=5).defer("headline")
The order in which fields are added to the deferred set does not matter. Calling ``defer()`` with a field name that has already been deferred is harmless (the field will still be deferred). The order in which fields are added to the deferred set does not matter. Calling ``defer()`` with a field name that has already been deferred is harmless (the field will still be deferred).
@ -919,7 +920,7 @@ immediately; the remainder are deferred. Thus, successive calls to ``only()``
result in only the final fields being considered:: result in only the final fields being considered::
# This will defer all fields except the headline. # This will defer all fields except the headline.
Entry.objects.only("body", "lede").only("headline") Entry.objects.only("body", "rating").only("headline")
Since ``defer()`` acts incrementally (adding fields to the deferred list), you Since ``defer()`` acts incrementally (adding fields to the deferred list), you
can combine calls to ``only()`` and ``defer()`` and things will behave can combine calls to ``only()`` and ``defer()`` and things will behave