#26630: Defered constraint checks flush after `post_delete` signal
-------------------------------------+-------------------------------------
Reporter: Alex Madjar | Owner: (none)
Type: Bug | Status: assigned
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Annabelle Wiegart):
Thank you for your clarifications, Jacob. i looked at the DryORM example
and a bit into the Collector class and the "fast delete" path.
I'm a bit unsure about the expected behavior though. The ticket
description says "Expectation: a.F_id is None". Since the "fast delete"
path leads to the deletion of `a` not being deferred, I suppose the
expected behavior would be exactly this, even if a `post_delete` signal is
attached to `Choice` as well?
--
Ticket URL: <https://code.djangoproject.com/ticket/26630#comment:10>
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/0107019bb6b6675c-3d5f24ce-3e56-4ab1-b42e-c5503ad3fd6a-000000%40eu-central-1.amazonses.com.
