#22802: update Atomic class to make use of public transaction module-level API
functions
-------------------------------------+-------------------------------------
     Reporter:  gwilson              |                    Owner:  gwilson
         Type:                       |                   Status:  assigned
  Cleanup/optimization               |                  Version:  1.6
    Component:  Database layer       |               Resolution:
  (models, ORM)                      |             Triage Stage:
     Severity:  Normal               |  Unreviewed
     Keywords:                       |      Needs documentation:  0
    Has patch:  0                    |  Patch needs improvement:  0
  Needs tests:  0                    |                    UI/UX:  0
Easy pickings:  0                    |
-------------------------------------+-------------------------------------
Description changed by gwilson:

Old description:

> 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.

New description:

 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 be 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#comment:4>
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/065.7955cb5b8b73696d2d2c27ac3b41523f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to