On Jun 27, 5:56 pm, Ian Bicking <[EMAIL PROTECTED]> wrote:
> * Way for a library to get "the" transaction manager.
> * Interface for that transaction manager, maybe copied from Zope.
> * Single convention for how to specify a database connection (ideally
> string-based).
> * Probably a way to get "the" configuration, so you can lazily get a
> connection based on the configured connection.
just as a point of reference, here is zalchemy's integration of Zope
datamanager:
http://svn.zope.org/z3c.zalchemy/trunk/src/z3c/zalchemy/datamanager.py?rev=77165&view=auto
I would favor that the interface supports two-phase semantics like
zope's. sqlalchemy's "flush()" model already fits in pretty well with
the two-phase model, and will eventually be building explicit "two-
phase" hooks into SQLAlchemy's engine and session, with real
implementations for postgres to start with.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pylons-discuss" 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 this group at
http://groups.google.com/group/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---
