#15522: delete_model on admin delete action
-------------------------------+------------------------------------
Reporter: Divad | Owner: nobody
Type: New feature | Status: new
Component: contrib.admin | Version: master
Severity: Normal | Resolution:
Keywords: delete_model | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 1
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------+------------------------------------
Comment (by czpython):
While I agree that we should keep consistency, in this case I think both
actions should be treated separately.
One deletes a single object, the other deletes multiple objects.
Hooking a pre delete signal or calling delete_model have big impact on
performance depending on how many objects
are being deleted.
I'd like to propose a change in the delete action that allows for hooking
into it before the deletion takes place,
maybe a method in the {{{ModelAdmin}}} class?
--
Ticket URL: <https://code.djangoproject.com/ticket/15522#comment:13>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.bebbe3e4da96d64e535b74050caa427f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
