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

Added a short note to the modelforms documentation linking between 

save(commit=False) and using force_insert or force_update on the Model.save()
call. Refs #8672.


git-svn-id: http://code.djangoproject.com/svn/django/trunk@9539 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Malcolm Tredinnick 2008-12-02 04:07:43 +00:00
parent 81c8b3c696
commit f7a64b341a
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
docs/topics/forms/modelforms.txt
View File

@ -196,7 +196,8 @@ accepts either ``True`` or ``False``. If you call ``save()`` with
``commit=False``, then it will return an object that hasn't yet been saved to
the database. In this case, it's up to you to call ``save()`` on the resulting
model instance. This is useful if you want to do custom processing on the
object before saving it. ``commit`` is ``True`` by default.
object before saving it, or if you want to use on of the specialised
:ref:`model saving options <ref-models-force-insert>`. ``commit`` is ``True`` by default.
Another side effect of using ``commit=False`` is seen when your model has
a many-to-many relation with another model. If your model has a many-to-many