diff options
| author | Malcolm Tredinnick <malcolm.tredinnick@gmail.com> | 2008-12-02 04:07:43 +0000 |
|---|---|---|
| committer | Malcolm Tredinnick <malcolm.tredinnick@gmail.com> | 2008-12-02 04:07:43 +0000 |
| commit | f7a64b341acb1a77e53a91b5298a3117abbfd1ea (patch) | |
| tree | 2c3ee8270cc6079698147578b0ac8a82367d10f8 /docs/topics/forms | |
| parent | 81c8b3c69668ca17d36a7d4e737572b4f9aadfd9 (diff) | |
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
Diffstat (limited to 'docs/topics/forms')
| -rw-r--r-- | docs/topics/forms/modelforms.txt | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/docs/topics/forms/modelforms.txt b/docs/topics/forms/modelforms.txt index 3cbb66068f..49c17fc556 100644 --- a/docs/topics/forms/modelforms.txt +++ b/docs/topics/forms/modelforms.txt @@ -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 |