django/django
1
1
Fork 0
mirror of https://github.com/django/django.git synced 2025-10-30 23:47:49 +03:00
Code Issues Packages Projects Releases Wiki Activity

Fixed #4175 -- Fixed a couple of ReST markup errors. Thanks, Matt McClanahan.

Browse Source 
git-svn-id: http://code.djangoproject.com/svn/django/trunk@5120 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Malcolm Tredinnick 2007-04-28 14:23:41 +00:00
parent d9cc22b3e3
commit fe0f238841
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/db-api.txt
View File

@ -112,7 +112,7 @@ the previous record in the database::
b4 = Blog(id=3, name='Not Cheddar', tagline='Anything but cheese.') b4 = Blog(id=3, name='Not Cheddar', tagline='Anything but cheese.')
b4.save() # Overrides the previous blog with ID=3! 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. happens.
Explicitly specifying auto-primary-key values is mostly useful for bulk-saving 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 The following ``QuerySet`` methods evaluate the ``QuerySet`` and return
something *other than* a ``QuerySet``. 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. they query the database each time they're called.
``get(**kwargs)`` ``get(**kwargs)``
@ -906,8 +906,8 @@ The database API supports the following lookup types:
exact exact
~~~~~ ~~~~~
Exact match. If the value provided for comparison is ``None``, it will Exact match. If the value provided for comparison is ``None``, it will
be interpreted as an SQL ``NULL`` (See isnull_ for more details). be interpreted as an SQL ``NULL`` (See isnull_ for more details).
Examples:: Examples::