Author: jezdez
Date: 2010-02-21 18:43:10 -0600 (Sun, 21 Feb 2010)
New Revision: 12479

Modified:
   django/branches/releases/1.1.X/docs/ref/models/querysets.txt
Log:
[1.1.X] Fixed #12620 - Refer to better fieldname in defer docs. Thanks, dwillis.

Backport of r12462.

Modified: django/branches/releases/1.1.X/docs/ref/models/querysets.txt
===================================================================
--- django/branches/releases/1.1.X/docs/ref/models/querysets.txt        
2010-02-22 00:42:51 UTC (rev 12478)
+++ django/branches/releases/1.1.X/docs/ref/models/querysets.txt        
2010-02-22 00:43:10 UTC (rev 12479)
@@ -804,7 +804,7 @@
 
 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,7 +814,7 @@
 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).
 
@@ -822,7 +822,7 @@
 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()``::

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Reply via email to