diff options
| author | Malcolm Tredinnick <malcolm.tredinnick@gmail.com> | 2008-12-02 06:00:44 +0000 |
|---|---|---|
| committer | Malcolm Tredinnick <malcolm.tredinnick@gmail.com> | 2008-12-02 06:00:44 +0000 |
| commit | 931d96e065fd872e759b0c53cd1f38be59fdca64 (patch) | |
| tree | ee2bbe303d9397b53e297bda620f77d7a5b206bb /docs | |
| parent | 19cb720df755b8ab9717b4e5693a08967ef68655 (diff) | |
[1.0.X] 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.
Backport of r9539 from trunk.
git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.0.X@9541 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs')
| -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 |