|
From: Christian M. S. <chr...@st...> - 2005-09-02 07:51:02
|
Hi, On Thursday 01 September 2005 23.32, Markus Hoenicka wrote: > [I've cc'ed the list as this is of general interest. Please keep these > discussions on the list. The discussion will be archived and it is > open for everyone to join in] > > Henrique writes: > > The functions proposed was: > > > > dbi_conn_commit(dbi_connt conn); > > dbi_conn_rollback(dbi_conn conn, const char > > *savepoint); > > dbi_conn_rollback_all(dbi_conn conn); > > dbi_conn_set_savepoint(dbi_conn conn, const char > > *savepoint); > > > > Though, I think that we "must" offers a "native" > > transactions support instead "const strings" > > savepoints, something like creating a new > > dbi_transaction data type, what do you think? I don't see a reson for this. The engines will handle transactions internaly the only thing needed to be provided by the libdbi user is the name of the savepoint so that she/he can rollback with that savepoint as an argument. A transcation will only be tied to a connection anyway so why extract it in to some other level where it doesn't belong? I think the interface provided in your email is a sane way of implementing transaction support. Regards, Christian |