From 07e594bba22caa3f02023d0010ae5a6fb99773f0 Mon Sep 17 00:00:00 2001
From: David Sanders <dsanders@rapilabs.com>
Date: Tue, 29 Sep 2015 12:09:57 +1000
Subject: [PATCH] [1.8.x] Clarified that Model.delete() isn't called as a
result of a cascading delete.
Backport of 5c6316dc3467fd7b669bea9157f591ac5fd00ec4 from master
---
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 f7bddf4eb0..25230b1711 100644
--- a/docs/topics/db/models.txt
+++ b/docs/topics/db/models.txt
@@ -825,9 +825,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<topics-db-queries-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.
+ QuerySet <topics-db-queries-delete>` or as a result of a :attr:`cascading
+ delete <django.db.models.ForeignKey.on_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<django.db.models.query.QuerySet.bulk_create>` or