#36217: post_save signal is not called when LogEntry has Deletion action
-------------------------------------+-------------------------------------
Reporter: smiling-watermelon | Owner: (none)
Type: Bug | Status: new
Component: contrib.admin | Version: 5.1
Severity: Release blocker | Resolution:
Keywords: LogEntry Signals | Triage Stage: Accepted
post_save |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Sarah Boyce):
> So, does that mean that from now on, bulk_create will always be used
regardless of the number of objects being added or changed, and signals
will never be triggered?
Right now, `save()`, which sends the signals, is used when
`single_object=True`.
This is used by `log_addition` and `log_change`. This is not used by
`log_deletions` (which makes sense as it can have multiple objects).
But `log_deletions` is called with a single object in
`django.contrib.admin.options.ModelAdmin._delete_view`. To me, it is
inconsistent that we use `save` and send signals in the other cases, but
not here.
--
Ticket URL: <https://code.djangoproject.com/ticket/36217#comment:3>
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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/010701954bf1eac5-21231611-b395-4a0a-9619-c85cd0c01a41-000000%40eu-central-1.amazonses.com.
