#23056 closed Bug (invalid)

Queryset.delete always triggers pre/post delete signal?

Reported by: flisky Owned by: nobody
Component: Documentation Version: master
Severity: Normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

It seems that the doc https://docs.djangoproject.com/en/dev/topics/db/queries/#deleting-objects has not synced with the commit https://github.com/django/django/commit/1cd6e04c.

Change History (2)

comment:1 Changed 11 months ago by claudep

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset

Sorry, but could you please be a little more specific about what you want to see changed in that documentation?

comment:2 Changed 10 months ago by flisky

  • Resolution set to invalid
  • Status changed from new to closed

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!

Note: See TracTickets for help on using tickets.
Back to Top