Browse files

Fixed #11022: documented that the admin bulk delete action calls `Que…

…rySet.delete()`, not `Model.delete()`. Thanks, Idan Gazit.

git-svn-id: bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
1 parent e508bfd commit 5bdee2556e9f6b32dee8bb25ffc9594a3cb23472 @jacobian jacobian committed May 14, 2009
Showing with 13 additions and 0 deletions.
  1. +13 −0 docs/ref/contrib/admin/actions.txt
@@ -23,7 +23,20 @@ models. For example, here's the user module from Django's built-in
:mod:`django.contrib.auth` app:
.. image:: _images/user_actions.png
+.. warning::
+ The "delete selected objects" action uses :meth:`QuerySet.delete()
+ <django.db.models.QuerySet.delete>` for efficiency reasons, which has an
+ important caveat: your model's ``delete()`` method will not be called.
+ If you wish to override this behavior, simply write a custom action which
+ accomplishes deletion in your preferred manner -- for example, by calling
+ ``Model.delete()`` for each of the selected items.
+ For more background on bulk deletion, see the documentation on :ref:`object
+ deletion <topics-db-queries-delete>`.
Read on to find out how to add your own actions to this list.
Writing actions

0 comments on commit 5bdee25

Please sign in to comment.