diff options
Diffstat (limited to 'docs/db-api.txt')
| -rw-r--r-- | docs/db-api.txt | 21 |
1 files changed, 12 insertions, 9 deletions
diff --git a/docs/db-api.txt b/docs/db-api.txt index feeb708be0..a3b62e87aa 100644 --- a/docs/db-api.txt +++ b/docs/db-api.txt @@ -121,19 +121,22 @@ 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** + +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 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:: +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 -A raw save saves all the data in your object, but performs no pre-save processing -on the data in the object. +A raw save saves all the data in your object, but performs no pre-save processing +on the data in the object. Saving changes to objects ========================= |