Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Browse files

Fixed #6915: Documented the fact that QuerySet.delete() may not call …

…delete() methods of individual objects

git-svn-id: bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
commit ceb8fc56af635445cf985eeb60e14a8763dd56cb 1 parent cbcc415
@ubernostrum ubernostrum authored
Showing with 9 additions and 0 deletions.
  1. +9 −0 docs/db-api.txt
9 docs/db-api.txt
@@ -2229,6 +2229,15 @@ For example, this deletes all ``Entry`` objects with a ``pub_date`` year of
+Keep in mind that this will, whenever possible, be executed purely in
+SQL, and so the ``delete()`` methods of individual object instances
+will not necessarily be called during the process. If you've provided
+a custom ``delete()`` method on a model class and want to ensure that
+it is called, you will need to "manually" delete instances of that
+model (e.g., by iterating over a ``QuerySet`` and calling ``delete()``
+on each object individually) rather than using the bulk ``delete()``
+method of a ``QuerySet``.
When Django deletes an object, it emulates the behavior of the SQL
constraint ``ON DELETE CASCADE`` -- in other words, any objects which
had foreign keys pointing at the object to be deleted will be deleted
Please sign in to comment.
Something went wrong with that request. Please try again.