Re: [Firebird-net-provider] Normal or retained commit/rollback of transactions

[<car...@te...>]

Hello:

 > I studied code of FbTransaction and found that Rollback() and 
Commit() use
 > the *_retaining version for committing / rolling back transactions. 
After a
 > retained commit/rollback automatically a "new" transaction is started,
 > indicated by a transaction state of TxnState.TRANSACTION_STARTED. Now, a
 > call to FbConnection.BeginTransaction() failes.



I make this after see documentation of SqlClient, OleDb, And Odbc .Net 
providers by Microsoft that doesn´t allow parallel transactions, i want 
to make this the most conmpaitble as possible with other .net providers.

 > But this is, in my opinion, not what the normal developer expect 
(compared
 > to other RDBMS). Also, the retained commit/rollback preserves the 
snapshot
 > of the former transaction, which again may not result in a behavior
 > comparable to other RDBMS.
 >
 > I propose to introduce a property to the connection and/or transaction
 > objects to set the commit/rollback mode to retaining or normal. In normal
 > mode, the Commit()/Rollback() methods must call the standard
 > GDS-transaction-functions and set the TxnState to TxnState.NOTRANSACTION.
 > For retaining mode, the behavior is acceptable like it is now.



This can be a good idea i can see how other providers manage commiting 
and rollbacking transactions.




Best regards
Carlos Guzmán Álvarez
Vigo-Spain

 >
 > Just my thoughts on that topic, any comments welcome.
 >
 > -- Joja
 >
 >
 >
 > -------------------------------------------------------
 > This sf.net email is sponsored by:ThinkGeek
 > Welcome to geek heaven.
 > http://thinkgeek.com/sf
 > _______________________________________________
 > Firebird-net-provider mailing list
 > Fir...@li...
 > https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
 >