#22802: update Atomic class to make use of public transaction module-level API
functions
-------------------------------------+-------------------------------------
Reporter: gwilson | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version: master
Component: Database | Keywords:
layer (models, ORM) | Has patch: 0
Severity: Normal | Needs tests: 0
Triage Stage: | Easy pickings: 0
Unreviewed |
Needs documentation: 0 |
Patch needs improvement: 0 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
Currently, the class operates using the connection object directly;
however, this makes it more difficult for libraries that need to customize
transaction management, e.g. https://github.com/jmoiron/johnny-cache (see
also https://github.com/jmoiron/johnny-cache/issues/40).
Ideally, I believe that wrapping the entire transaction API into a class
and making it configurable would even better, as it would allow for
transaction management customization without monkey patching. That said,
I propose we at least make use of the public API functions for the 1.7
release, as that makes the transactions interface backwards-compatible
with versions before the Atomic class landed.
--
Ticket URL: <https://code.djangoproject.com/ticket/22802>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/050.de7c176d39c1a83428827541f91a4def%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
