RFC: connection transaction convenience

I often want to use a connection's transaction manager, as in:

  conn.transaction_manager.commit()

I do this:

- Interactively **a lot**.  I get really tired of typing
transaction_manager (even with completion).

- Occasionally in lower-level code where I need to affect transaction
lifecycle, but don't want to have the low-level code to assume the use
of a thread-local transaction manager.

I propose as a convenience:

- add begin as an alias for sync.

- Allow commit and abort to be called without arguments to commit and
abort the current transaction.

  (They're currently called with a transaction as part of the
IDataManager API.)

Thoughts?

Jim

-- 
Jim Fulton
http://jimfulton.info

-- 
You received this message because you are subscribed to the Google Groups "zodb" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.