Opened 10 years ago

Last modified 9 years ago

#13251 new New feature

Add ability to know where an object was deleted from to pre/post delete signals

Reported by: skoom Owned by: nobody
Component: Database layer (models, ORM) Version: master
Severity: Normal Keywords: signals
Cc: Triage Stage: Accepted
Has patch: yes Needs documentation: yes
Needs tests: yes Patch needs improvement: no
Easy pickings: no UI/UX: no


Since deleting objects deletes related objects, it would be good to know the origin of the delete.

It lets the signal listeners know why an object is being delete. If it's deleted from a model.delete(), you know which instance initiated the delete and if it's from a queryset.delete() you know which queryset initiated the delete, with the models in that queryset. Using this you know if the instance is being deleted directly or because it's related to another instance.

Attachments (1)

changes.patch (2.6 KB) - added by skoom 10 years ago.

Download all attachments as: .zip

Change History (9)

Changed 10 years ago by skoom

Attachment: changes.patch added

comment:1 Changed 10 years ago by skoom

Needs documentation: set

comment:2 Changed 10 years ago by anonymous

Needs tests: set

comment:3 Changed 10 years ago by Russell Keith-Magee

Component: Core frameworkDatabase layer (models, ORM)
Triage Stage: UnreviewedAccepted

comment:4 Changed 9 years ago by Julien Phalip

See a possibly related issue in #6870.

comment:5 Changed 9 years ago by Luke Plant

Type: New feature

comment:6 Changed 9 years ago by Luke Plant

Severity: Normal

comment:7 Changed 8 years ago by Aymeric Augustin

UI/UX: unset

Change UI/UX from NULL to False.

comment:8 Changed 8 years ago by Aymeric Augustin

Easy pickings: unset

Change Easy pickings from NULL to False.

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