#18100: Deleting model instances with deferred fields don't trigger deletion
signals
-------------------------------------+-------------------------------------
Reporter: charettes | Owner: charettes
Type: Bug | Status: assigned
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: deferred delete | Triage Stage: Ready for
signals | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette <charette.s@…>):
In [changeset:"535660b852c8899a17b82d20a06c926d8d437db3" 535660b8]:
{{{
#!CommitTicketReference repository=""
revision="535660b852c8899a17b82d20a06c926d8d437db3"
Refs #18100 -- Added tests for deferred model deletion signals.
Thanks Tim for the review and pointing out this was fixed by #26207.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/18100#comment:14>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.a06f3736333de5e5d8e542302a3bf663%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
