#14051: Signals for transaction commit/rollback
-------------------------------------+-------------------------------------
Reporter: Ask Solem <ask@…> | Owner: nobody
Type: New feature | Status: reopened
Component: Database layer | Version: 1.3
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Design
Keywords: | decision needed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Kronuz):
* cc: Kronuz (added)
Comment:
If implementing `post_commit` and `post_rollback` signals, I think one
also has to think about savepoints. `pre_rollback` signals connected
during rolled back savepoints should still be called at commit time,
whilst analogously connected `post_commit` signals should not, potentially
ending up with both `post_commit` and `post_rollback` signals being called
during a `transaction.commit()` call, but only `post_rollback` signals
during a `transaction.rollback()` call. Note this behavior is not yet
implemented in django-transaction-signals.
--
Ticket URL: <https://code.djangoproject.com/ticket/14051#comment:24>
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 [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit https://groups.google.com/groups/opt_out.
