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|
|Has patch:||yes||Needs documentation:||yes|
|Needs tests:||yes||Patch needs improvement:||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.
Change History (9)
Changed 5 years ago by skoom
comment:1 Changed 5 years ago by skoom
- Needs documentation set
- Needs tests unset
- Patch needs improvement unset
comment:3 Changed 5 years ago by russellm
- Component changed from Core framework to Database layer (models, ORM)
- Triage Stage changed from Unreviewed to Accepted