From 5bdee2556e9f6b32dee8bb25ffc9594a3cb23472 Mon Sep 17 00:00:00 2001 From: Jacob Kaplan-Moss Date: Thu, 14 May 2009 02:35:16 +0000 Subject: [PATCH] Fixed #11022: documented that the admin bulk delete action calls `QuerySet.delete()`, not `Model.delete()`. Thanks, Idan Gazit. git-svn-id: http://code.djangoproject.com/svn/django/trunk@10780 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/ref/contrib/admin/actions.txt | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/docs/ref/contrib/admin/actions.txt b/docs/ref/contrib/admin/actions.txt index 7b664f901d..904d20eb33 100644 --- a/docs/ref/contrib/admin/actions.txt +++ b/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() + ` 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 `. + Read on to find out how to add your own actions to this list. Writing actions