Author: lukeplant
Date: 2010-07-05 11:26:12 -0500 (Mon, 05 Jul 2010)
New Revision: 13419

Modified:
   django/trunk/docs/topics/db/optimization.txt
Log:
Small corrections/improvements to DB optimization docs.



Modified: django/trunk/docs/topics/db/optimization.txt
===================================================================
--- django/trunk/docs/topics/db/optimization.txt        2010-07-02 19:14:58 UTC 
(rev 13418)
+++ django/trunk/docs/topics/db/optimization.txt        2010-07-05 16:26:12 UTC 
(rev 13419)
@@ -5,7 +5,7 @@
 ============================
 
 Django's database layer provides various ways to help developers get the most
-out of their databases. This documents gathers together links to the relevant
+out of their databases. This document gathers together links to the relevant
 documentation, and adds various tips, organized under an number of headings 
that
 outline the steps to take when attempting to optimize your database usage.
 
@@ -108,9 +108,8 @@
 
 For instance:
 
-* At the most basic level, use :ref:`filter and exclude <queryset-api>` to
-  filtering in the database to avoid loading data into your Python process, 
only
-  to throw much of it away.
+* At the most basic level, use :ref:`filter and exclude <queryset-api>` to do
+  filtering in the database.
 
 * Use :ref:`F() object query expressions <query-expressions>` to do filtering
   against other fields within the same model.
@@ -245,9 +244,6 @@
 added for these methods will not be executed, including anything driven from 
the
 normal database object :ref:`signals <ref-signals>`.
 
-Don't retrieve things you already have
-======================================
-
 Use foreign key values directly
 -------------------------------
 

-- 
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.

Reply via email to