Jojakim Stahl wrote:
> Hello!
>
> A got the new CVS version and had problems to call
> FbConnection.BeginTransaction() a second time after disposing the
> FbTransaction-object returned by the first call.
> I studied code and found that FbTransaction.Dispose() doesn't reset the
> active transaction object of the connection. Due to the simple test for
> activeTxn != null when calling FbConnection.BeginTransaction() the second
> call throws.
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.
> I added an internal property to FbTransaction to query the transactions
> state and extended the test in FbConnection.BeginTransaction() to
> check the
> state.
Thanks very much ;), i´m seeing now how other providers manage this
issue, can you send the patches withh diff -u please.
Best regards
Carlos Guzmán Álvarez
Vigo-Spain
|
