From 08cec1f5088a050730a70a1eee6bb0263a4892f5 Mon Sep 17 00:00:00 2001 From: Timo Graham Date: Mon, 27 Dec 2010 23:46:06 +0000 Subject: [PATCH] Fixed #12313 - Add a note that QuerySet.delete() doesn't necessarily call obj.delete(). thanks FunkyELF for the suggestion. git-svn-id: http://code.djangoproject.com/svn/django/trunk@15071 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/topics/db/models.txt | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/topics/db/models.txt b/docs/topics/db/models.txt index 17d66d777a0..f276bc01084 100644 --- a/docs/topics/db/models.txt +++ b/docs/topics/db/models.txt @@ -751,6 +751,14 @@ built-in model methods, adding new arguments. If you use ``*args, **kwargs`` in your method definitions, you are guaranteed that your code will automatically support those arguments when they are added. +.. admonition:: Overriding Delete + + Note that the :meth:`~Model.delete()` method for an object is not + necessarily called when :ref:`deleting objects in bulk using a + QuerySet`. To ensure customized delete logic + gets executed, you can use :data:`~django.db.models.signals.pre_save` + and/or :data:`~django.db.models.signals.post_save` signals. + Executing custom SQL --------------------