test0908
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Edited docs/db-api.txt changes from [5658] 

git-svn-id: http://code.djangoproject.com/svn/django/trunk@5698 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Adrian Holovaty 2007-07-14 16:58:54 +00:00
parent f9d27b5d0b
commit 0f869d1124
1 changed files with 12 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
docs/db-api.txt
View File

@ -121,14 +121,17 @@ objects, when you're confident you won't have primary-key collision.
Raw saves
---------
When you save an Django object, some pre-processing will occur on the the data
that is in the object. For example, if your model has a ``DateField`` with
``auto_now=True`` set, the pre-save phase will alter the data in the object
to ensure that the date field contains the current date stamp.
**New in Django development version**
Although these automated changes can be very useful, there will be times when
you just want to save the data as-is. In these cases, you can invoke a *Raw Save*
by passing ``raw=True`` as an argument to the ``save()`` method::
When you save an Django object, some pre-processing might occur on the the
object's data before it's saved to the database. For example, if your model has
a ``DateField`` with ``auto_now=True`` set, the pre-save phase will alter the
data in the object to ensure that the date field contains the current date
stamp.
Although these automated changes can be useful, sometimes you just want to save
the data as-is. In these cases, you can invoke a **raw save** by passing
``raw=True`` as an argument to the ``save()`` method::
b4.save(raw=True) # Saves object, but does no pre-processing