diff options
| author | David Sanders <dsanders@rapilabs.com> | 2015-09-29 12:09:57 +1000 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2015-09-30 08:44:04 -0400 |
| commit | 5c6316dc3467fd7b669bea9157f591ac5fd00ec4 (patch) | |
| tree | f886290f095a1c4ed4a333c4cdbb26391f43cd70 | |
| parent | b47552b445547e60cc89213f79e02333cb63f270 (diff) | |
Clarified that Model.delete() isn't called as a result of a cascading delete.
| -rw-r--r-- | docs/topics/db/models.txt | 8 |
1 files 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<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 |