From 2d854539c327b3630265bec10263ae61ce81d202 Mon Sep 17 00:00:00 2001 From: Timo Graham Date: Fri, 31 Dec 2010 13:10:05 +0000 Subject: [PATCH] [1.2.X] Fixed #14997 - A typo in "Overriding delete". thanks phunehehe for the report. Backport of r15117 from trunk. git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.2.X@15118 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/topics/db/models.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/topics/db/models.txt b/docs/topics/db/models.txt index f90a8d177b..be3b64847f 100644 --- a/docs/topics/db/models.txt +++ b/docs/topics/db/models.txt @@ -756,8 +756,8 @@ code will automatically support those arguments when they are added. 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. + gets executed, you can use :data:`~django.db.models.signals.pre_delete` + and/or :data:`~django.db.models.signals.post_delete` signals. Executing custom SQL --------------------