#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):
I'm unable to reproduce the described behavior with the attached sample
project. The related Choice instance seems to be deleted immediately. The
post_delete callback function produces the error
`t26630.models.Choice.DoesNotExist: Choice matching query does not exist`.
Is there still a bug that needs to be fixed?
--
Ticket URL: <https://code.djangoproject.com/ticket/26630#comment:8>
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/0107019b9e7496bf-c60fd06d-b334-4e38-b67b-4060e34bffd6-000000%40eu-central-1.amazonses.com.
