Author: lukeplant
Date: 2010-12-31 09:48:51 -0600 (Fri, 31 Dec 2010)
New Revision: 15123
Modified:
django/branches/releases/1.2.X/docs/topics/db/optimization.txt
Log:
[1.2.X] Some small fixes to DB optimization docs.
Backport of [15122] from trunk.
Modified: django/branches/releases/1.2.X/docs/topics/db/optimization.txt
===================================================================
--- django/branches/releases/1.2.X/docs/topics/db/optimization.txt
2010-12-31 15:47:46 UTC (rev 15122)
+++ django/branches/releases/1.2.X/docs/topics/db/optimization.txt
2010-12-31 15:48:51 UTC (rev 15123)
@@ -191,7 +191,7 @@
If you are going to need other data from the QuerySet, just evaluate it.
-For example, assuming an Email class that has a ``body`` attribute and a
+For example, assuming an Email model that has a ``body`` attribute and a
many-to-many relation to User, the following template code is optimal:
.. code-block:: html+django
@@ -212,7 +212,8 @@
It is optimal because:
- 1. Since QuerySets are lazy, this does no database if 'display_inbox' is
False.
+ 1. Since QuerySets are lazy, this does no database queries if 'display_inbox'
+ is False.
#. Use of ``with`` means that we store ``user.emails.all`` in a variable for
later use, allowing its cache to be re-used.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
