summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorJacob Kaplan-Moss <jacob@jacobian.org>2005-07-14 21:04:21 +0000
committerJacob Kaplan-Moss <jacob@jacobian.org>2005-07-14 21:04:21 +0000
commit5fc13947fcd6c3f3569ce8b643030a645b108037 (patch)
tree2215abeef3ae8431f7c87b73697496323c88978c /docs
parent26c6566215ebc9407f3c40643ff907ac5084f3c1 (diff)
Fixed a couple of bugs in the docs.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@39 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs')
-rw-r--r--docs/db-api.txt7
1 files changed, 4 insertions, 3 deletions
diff --git a/docs/db-api.txt b/docs/db-api.txt
index b97018b46e..193cbf2b22 100644
--- a/docs/db-api.txt
+++ b/docs/db-api.txt
@@ -197,7 +197,7 @@ For example, using the Poll and Choice models from above, if you do the followin
Then subsequent calls to ``c.get_poll()`` won't hit the database.
Note that ``select_related`` follows foreign keys as far as possible. If you have the
-following models...
+following models::
class Poll(meta.Model):
...
@@ -214,8 +214,8 @@ following models...
...
)
-...then a call to ``singlevotes.get_object(id__exact=4, select_related=True)`` will
-cache the related choice *and* the related poll.
+then a call to ``singlevotes.get_object(id__exact=4, select_related=True)`` will
+cache the related choice *and* the related poll::
>>> sv = singlevotes.get_object(id__exact=4, select_related=True)
>>> c = sv.get_choice() # Doesn't hit the database.
@@ -290,3 +290,4 @@ For example::
Creating new objects
====================
+... \ No newline at end of file