Ticket #23732: 23732.diff

docs/ref/models/querysets.txt

@@ -754 +754 @@
     # in the previous query.
     b = e.blog
 
+Here's another example that shows there is no need to use ``get()`` after
+``select_related()`` (just in case you got that impression from the example
+above)::
+
+    # Find all the blogs with entries scheduled to be published in the future.
+    blogs = set()
+
+    for e in Entry.objects.filter(pub_date__gt=timezone.now()).select_related('blog'):
+        # Without select_related(), this would make a database for each
+        # loop iteration in order to fetch the related blog for each entry.
+        blogs.add(e.blog)
+
 You can follow foreign keys in a similar way to querying them. If you have the
 following models::
 
@@ -771 +783 @@
         # ...
         author = models.ForeignKey(Person)
 
-... then a call to ``Book.objects.select_related('person__city').get(id=4)``
+... then a call to ``Book.objects.select_related('author__hometown').get(id=4)``
 will cache the related ``Person`` *and* the related ``City``::
 
-    b = Book.objects.select_related('person__city').get(id=4)
+    b = Book.objects.select_related('author__hometown').get(id=4)
     p = b.author         # Doesn't hit the database.
     c = p.hometown       # Doesn't hit the database.