diff options
| author | Tim Graham <timograham@gmail.com> | 2012-10-12 16:45:45 -0700 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2012-10-12 16:45:45 -0700 |
| commit | 5fb22329a14695419f191da8b7d0b5b22793aff0 (patch) | |
| tree | 65a675b024fec0bec32375fc6fff782e52d227df /docs | |
| parent | c870cb48cd0ec4b5dfdc5df95e6f0b5f5f8a738b (diff) | |
| parent | 443999a1eeea70e4deebcf31f8f845696be62c3d (diff) | |
Merge pull request #422 from elvard/18996
Fixed #18996 - Clarified overriden model methods not called on bulk operations
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/topics/db/models.txt | 9 |
1 files changed, 8 insertions, 1 deletions
diff --git a/docs/topics/db/models.txt b/docs/topics/db/models.txt index beb62f049c..84b4c84061 100644 --- a/docs/topics/db/models.txt +++ b/docs/topics/db/models.txt @@ -764,7 +764,7 @@ built-in model methods, adding new arguments. If you use ``*args, **kwargs`` in your method definitions, you are guaranteed that your code will automatically support those arguments when they are added. -.. admonition:: Overriding Delete +.. admonition:: Overridden model methods are not called on bulk operations Note that the :meth:`~Model.delete()` method for an object is not necessarily called when :ref:`deleting objects in bulk using a @@ -772,6 +772,13 @@ code will automatically support those arguments when they are added. 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 + :meth:`updating<django.db.models.query.QuerySet.update>` objects in bulk, + since none of :meth:`~Model.save()`, + :data:`~django.db.models.signals.pre_save`, and + :data:`~django.db.models.signals.post_save` are called. + Executing custom SQL -------------------- |
