[DB-SIG] Two-phase commit API proposal (was Re: Any standard for two phase commit APIs?)
Federico Di Gregorio
fog at initd.org
Mon Jan 21 12:53:05 CET 2008
Il giorno lun, 21/01/2008 alle 20.35 +0900, James Henstridge ha scritto:
> MySQL appears to have a special API for performing a one-phase commit
> of an XA transaction:
> XA COMMIT xid ONE PHASE
> Perhaps an argument to xa_commit() would be appropriate here?
> Without the argument, the commit would be considered to be a
> ProgrammingError. That would reduce the chance of programmer error
> leading to data corruption.
Lets not make an API that has features useful on a single backend. I
suppose the necessity for a one-phase commit in a two-phase transaction
is rare. A simple API means early adoption by most of the adapters.
Federico Di Gregorio http://people.initd.org/fog
Debian GNU/Linux Developer fog at debian.org
INIT.D Developer fog at initd.org
We should forget about small efficiencies, say about 97% of the
time: premature optimization is the root of all evil. -- D.E.Knuth
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Questa =?ISO-8859-1?Q?=E8?= una parte del messaggio
Url : http://mail.python.org/pipermail/db-sig/attachments/20080121/2e57d56e/attachment.pgp
More information about the DB-SIG