diff options
| author | Ben Spaulding <ben@spaulding.im> | 2013-12-11 10:28:05 -0700 |
|---|---|---|
| committer | Simon Charette <charette.s@gmail.com> | 2013-12-11 14:39:29 -0500 |
| commit | de1d5d5df5238136e8cd114e36065857bee1ace4 (patch) | |
| tree | c54710636096c83121af1d8da616e8f636ab0318 | |
| parent | 7a2910d790baf6df417f7821f86caafd3b275f3c (diff) | |
[1.6.x] Fixed #21594 -- Added note about model formsets deleting objects.
This behavior has been fixed in 65e03a424e. refs #10284.
| -rw-r--r-- | docs/topics/forms/modelforms.txt | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/docs/topics/forms/modelforms.txt b/docs/topics/forms/modelforms.txt index 48e045442b..38784f9566 100644 --- a/docs/topics/forms/modelforms.txt +++ b/docs/topics/forms/modelforms.txt @@ -836,6 +836,12 @@ to the database. If your formset contains a ``ManyToManyField``, you'll also need to call ``formset.save_m2m()`` to ensure the many-to-many relationships are saved properly. +.. note:: + + While calling ``formset.save(commit=False)`` does not save new or changed + objects to the database, it *does* delete objects that have been marked for + deletion. This behavior will be corrected in Django 1.7. + .. _model-formsets-max-num: Limiting the number of editable objects |