From 5c6316dc3467fd7b669bea9157f591ac5fd00ec4 Mon Sep 17 00:00:00 2001 From: David Sanders Date: Tue, 29 Sep 2015 12:09:57 +1000 Subject: [PATCH] Clarified that Model.delete() isn't called as a result of a cascading delete. --- docs/topics/db/models.txt | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/topics/db/models.txt b/docs/topics/db/models.txt index 53d2396f03..99945d4287 100644 --- a/docs/topics/db/models.txt +++ b/docs/topics/db/models.txt @@ -835,9 +835,11 @@ 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_delete` - and/or :data:`~django.db.models.signals.post_delete` signals. + QuerySet ` or as a result of a :attr:`cascading + delete `. To ensure customized + delete logic gets executed, you can use + :data:`~django.db.models.signals.pre_delete` and/or + :data:`~django.db.models.signals.post_delete` signals. Unfortunately, there isn't a workaround when :meth:`creating` or