From 474e7dd6d08105fce66d7f62670a6c120c0b1198 Mon Sep 17 00:00:00 2001 From: Ben Spaulding Date: Wed, 11 Dec 2013 10:28:05 -0700 Subject: [PATCH] [1.4.x] Fixed #21594 -- Added note about model formsets deleting objects. This behavior has been fixed in 65e03a424e. refs #10284. Backport of de1d5d5df5 from stable/1.6.x. --- docs/topics/forms/modelforms.txt | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/topics/forms/modelforms.txt b/docs/topics/forms/modelforms.txt index 1aa7d6baaa..987d0875d7 100644 --- a/docs/topics/forms/modelforms.txt +++ b/docs/topics/forms/modelforms.txt @@ -668,6 +668,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