#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
-------------------------------------+-------------------------------------
Comment (by nicolas@…):
Hi,
As an alternative design, we can take inspiration from transaction
package.
http://www.zodb.org/zodbbook/transactions.html#data-managers
DataManagers are exactly what we need. They are useful to spread the
transaction calls to every backend that needs to be tight to the current
transaction.
By Backend I mean, it can be django.db.connection, The celery broker, or
even a simple transaction safe dictionary object.
--
Ticket URL: <https://code.djangoproject.com/ticket/14051#comment:25>
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.
