Browse files

[1.1.X] Fixed #12620 - Refer to better fieldname in defer docs. Thank…

…s, dwillis.

Backport of r12462.

git-svn-id: bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
1 parent 71897bf commit 4261efdc673c8034aa372b790e5c1c7e591d4fbc @jezdez jezdez committed Feb 22, 2010
Showing with 3 additions and 3 deletions.
  1. +3 −3 docs/ref/models/querysets.txt
@@ -804,7 +804,7 @@ the database.
This is done by passing the names of the fields to not load to ``defer()``::
- Entry.objects.defer("lede", "body")
+ Entry.objects.defer("headline", "body")
A queryset that has deferred fields will still return model instances. Each
deferred field will be retrieved from the database if you access that field
@@ -814,15 +814,15 @@ You can make multiple calls to ``defer()``. Each call adds new fields to the
deferred set::
# Defers both the body and lede fields.
- Entry.objects.defer("body").filter(headline="Lennon").defer("lede")
+ 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).
You can defer loading of fields in related models (if the related models are
loading via ``select_related()``) by using the standard double-underscore
notation to separate related fields::
- Blog.objects.select_related().defer("entry__lede", "entry__body")
+ Blog.objects.select_related().defer("entry__headline", "entry__body")
If you want to clear the set of deferred fields, pass ``None`` as a parameter
to ``defer()``::

0 comments on commit 4261efd

Please sign in to comment.