[DB-SIG] Two-phase commit API proposal (was Re: Any standard for two phase commit APIs?)

[James Henstridge]

On 21/01/2008, James Henstridge <james at jamesh.id.au> wrote:
> On 18/01/2008, James Henstridge <james at jamesh.id.au> wrote:
> > So is there any recommendations for what a two-phase commit API should
> > look like?
>
> I did a bit of investigation into a few databases, and came up with a
> proposal for an extension to the DB-API.

Here is an updated version of the proposal.  It removes the analysis
of the different databases, and updates the proposed API to match what
we've been discussing here.

I've added a section about what the "xid" arguments to the various
methods should look like.  That could probably do with some more
discussion as I am not too sure about it.

I've also included support for transaction recovery in the form of an
xa_recover() method and calling the xa_commit()/xa_rollback() methods
with a transaction ID as an argument.

James.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: two-phase-commit-v2.txt
Url: http://mail.python.org/pipermail/db-sig/attachments/20080121/82a9fb5f/attachment-0001.txt