Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

[1.2.X] Some small fixes to DB optimization docs.

Backport of [15122] from trunk.

git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.2.X@15123 bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
commit fa4ac6f80ca0417b04106626c854f09a6f15879d 1 parent 2d85453
@spookylukey spookylukey authored
Showing with 3 additions and 2 deletions.
  1. +3 −2 docs/topics/db/optimization.txt
View
5 docs/topics/db/optimization.txt
@@ -191,7 +191,7 @@ Don't overuse ``count()`` and ``exists()``
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 @@ many-to-many relation to User, the following template code is optimal:
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.

0 comments on commit fa4ac6f

Please sign in to comment.
Something went wrong with that request. Please try again.