diff options
| author | Tim Graham <timograham@gmail.com> | 2018-05-18 18:08:37 -0400 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2018-05-18 18:44:36 -0400 |
| commit | 452abf7b43e4d93911e277976b87411bb4b2a52c (patch) | |
| tree | fa4b9aef3b49d1189888e294999dbf4c61253fe5 | |
| parent | 7e875aa047095b4f57b9623425d8ea6a67e3d038 (diff) | |
[2.1.x] Fixed #29398 -- Doc'd that cascade deletion doesn't call delete() of related models.
Backport of e038f98bf342af716cf16e38be989c2d0f126797 from master
| -rw-r--r-- | docs/ref/models/fields.txt | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/docs/ref/models/fields.txt b/docs/ref/models/fields.txt index adb12aac63..c696b770b3 100644 --- a/docs/ref/models/fields.txt +++ b/docs/ref/models/fields.txt @@ -1257,6 +1257,11 @@ The possible values for :attr:`~ForeignKey.on_delete` are found in Cascade deletes. Django emulates the behavior of the SQL constraint ON DELETE CASCADE and also deletes the object containing the ForeignKey. + :meth:`.Model.delete` isn't called on related models, but the + :data:`~django.db.models.signals.pre_delete` and + :data:`~django.db.models.signals.post_delete` signals are sent for all + deleted objects. + * .. attribute:: PROTECT Prevent deletion of the referenced object by raising |