[DB-SIG] Any standard for two phase commit APIs?

[Stuart Bishop]

M.-A. Lemburg wrote:

> Now, if a database provides such an XA interface, this could
> also be made available to a Python TM. You'd then have to
> open the connection via this XA interface rather than the
> standard connection constructor (or pass in a parameter
> to this constructor to make it use the XA open instead of
> the RM open).
> 
> Perhaps we could piggy-back the XA-style interface onto
> the connection interface and its constructor and turn it
> into an XA DB-API extension ?!

If that has more than just 'prepare_transaction', 'commit_transaction' and
'rollback_transaction' it has no place in the DB-API IMO. These three
actions are the entirety of what PostgreSQL provides and are the building
blocks you need to build anything more complex (including XA). We don't need
driver authors  to build a transaction manager. We just need driver authors
to provide the building blocks for DB-API connections to be integrated with
transaction managers.


-- 
Stuart Bishop <stuart at stuartbishop.net>
http://www.stuartbishop.net/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: OpenPGP digital signature
Url : http://mail.python.org/pipermail/db-sig/attachments/20080118/4d4a31cd/attachment.pgp