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

[James Henstridge]

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.

I know that there are a few incomplete portions of the proposal, so
I'd appreciate feedback.  If you have knowledge of a database not
covered here, please comment on whether the proposed API would be
workable in that context.

Re: the confusion between "prepared transactions" vs. "prepared
statements" support, this probably won't conflict since the prepared
statement extensions I saw used Cursor.prepare() rather than
Connection.prepare().  If it is a problem though, the proposal could
be modified to use prepare_transaction() or similar.

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