#23056: Queryset.delete always triggers pre/post delete signal?
-------------------------------+--------------------------------------
Reporter: flisky | Owner: nobody
Type: Bug | Status: closed
Component: Documentation | Version: master
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by flisky):
* status: new => closed
* resolution: => invalid
Comment:
It's much clear for me to read it again with the queryset.delete API
reference.
If I have to say, I hope the following two mirror improvements as non-
native English reader.
First and most, could `when possible` be more informative?
Keep in mind that this will, whenever possible **(such as not handling
cascade nor pre_delete/post_delete signal connected)**, be executed purely
in SQL,
Second, the `not necessarily` is a little bit confusing for me at first.
and so the ``delete()`` methods of individual object instances will not
necessarily **and never** be called during the process.
Thanks!
--
Ticket URL: <https://code.djangoproject.com/ticket/23056#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.361dfbe4d6d862231d15661217169ef6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
