[1.6.x] Fixed #21594 -- Added note about model formsets deleting objects.
This behavior has been fixed in 65e03a424e
. refs #10284.
This commit is contained in:
parent
7a2910d790
commit
de1d5d5df5
|
@ -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
|
need to call ``formset.save_m2m()`` to ensure the many-to-many relationships
|
||||||
are saved properly.
|
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:
|
.. _model-formsets-max-num:
|
||||||
|
|
||||||
Limiting the number of editable objects
|
Limiting the number of editable objects
|
||||||
|
|
Loading…
Reference in New Issue