diff options
| author | Malcolm Tredinnick <malcolm.tredinnick@gmail.com> | 2007-04-28 14:23:41 +0000 |
|---|---|---|
| committer | Malcolm Tredinnick <malcolm.tredinnick@gmail.com> | 2007-04-28 14:23:41 +0000 |
| commit | fe0f2388417088dd98762c888e1da94aca3d759d (patch) | |
| tree | 227582a05ff5f28ddc578214b454c14d905ef2a4 | |
| parent | d9cc22b3e3b66f468c0df0d84ce54521ded79836 (diff) | |
Fixed #4175 -- Fixed a couple of ReST markup errors. Thanks, Matt McClanahan.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@5120 bcc190cf-cafb-0310-a4f2-bffc1f526a37
| -rw-r--r-- | docs/db-api.txt | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/db-api.txt b/docs/db-api.txt index d2aa6b8bb3..9d2f09daf3 100644 --- a/docs/db-api.txt +++ b/docs/db-api.txt @@ -112,7 +112,7 @@ the previous record in the database:: b4 = Blog(id=3, name='Not Cheddar', tagline='Anything but cheese.') b4.save() # Overrides the previous blog with ID=3! -See _`How Django knows to UPDATE vs. INSERT`, below, for the reason this +See `How Django knows to UPDATE vs. INSERT`_, below, for the reason this happens. Explicitly specifying auto-primary-key values is mostly useful for bulk-saving @@ -714,7 +714,7 @@ QuerySet methods that do not return QuerySets The following ``QuerySet`` methods evaluate the ``QuerySet`` and return something *other than* a ``QuerySet``. -These methods do not use a cache (see _`Caching and QuerySets` below). Rather, +These methods do not use a cache (see `Caching and QuerySets`_ below). Rather, they query the database each time they're called. ``get(**kwargs)`` @@ -906,8 +906,8 @@ The database API supports the following lookup types: exact ~~~~~ -Exact match. If the value provided for comparison is ``None``, it will -be interpreted as an SQL ``NULL`` (See isnull_ for more details). +Exact match. If the value provided for comparison is ``None``, it will +be interpreted as an SQL ``NULL`` (See isnull_ for more details). Examples:: |