#18094: `pre_delete` and `post_delete` signals are not correctly sent in
inheritance scenarios involving proxy models
-------------------------------------+-------------------------------------
Reporter: charettes | Owner: charettes
Type: Bug | Status: assigned
Component: Database layer | Version: 1.4
(models, ORM) | Resolution:
Severity: Normal | Triage Stage:
Keywords: model proxy multi- | Unreviewed
table inheritance signals delete | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by carljm):
@charettes - I think your summary of what signals ought to be sent here is
correct. Re the only/defer issue - if I'm not mistaken, that would be
fixed by the fix we are discussing here, correct? Given that, I'm not sure
it deserves it's own ticket, and I don't think we should put in place a
special-case fix for it.
@akaariai - Yeah, I think the question of consistency with save signals
and backwards compatibility is probably worth a thread on -developers -
I'll try to find time to post about it today.
--
Ticket URL: <https://code.djangoproject.com/ticket/18094#comment:9>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
