summaryrefslogtreecommitdiff
path: root/docs/topics
diff options
context:
space:
mode:
authorTimo Graham <timograham@gmail.com>2010-12-31 13:09:20 +0000
committerTimo Graham <timograham@gmail.com>2010-12-31 13:09:20 +0000
commitf2c4c63cdccd4883d3da8cfb9ff3bcd78406210d (patch)
tree410a93b89f5cc8c1509540f941c6e4f58c54c4ca /docs/topics
parentaff5c467c19ba9afd9d95d3a60e1a7c4eb8f25a3 (diff)
Fixed #14997 - A typo in "Overriding delete". thanks phunehehe for the report.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@15117 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs/topics')
-rw-r--r--docs/topics/db/models.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/topics/db/models.txt b/docs/topics/db/models.txt
index f276bc0108..9e73de73d8 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<topics-db-queries-delete>`. 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
--------------------