Fixed #18996 - Docs on overriden model methods
This commit is contained in:
parent
934f35f1f9
commit
443999a1ee
|
@ -762,7 +762,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
|
||||
|
@ -770,6 +770,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
|
||||
--------------------
|
||||
|
||||
|
|
Loading…
Reference in New Issue