Oracle transaction & Net 3.5sp1 bugs (but even for 2.0 sp2 , 3.0sp2)
That’s incredible, but true :D
the .net 3,5 SP1 introduce a strange behavior using transaction on a OracleDB connection.
From microsoft support (http://support.microsoft.com/kb/958484/en-us) :
“AutoCommit behavior in Oracle transactions is different in the .NET Framework 2.0 SP1 from the behavior in the .NET Framework 2.0 SP2. In the .NET Framework 2.0 SP2, if an application starts a transaction, completes the transaction, and then starts a new transaction on the same connection, all the commands that are executed in the second transaction execute in auto-commit mode. The changes that are made by those commands are committed to the database even if the transaction is rolled back”
uhmmm, it doesn’t sound good.. isnt’it ?
On the support page you will find a LONG list of issues solved by the patches..
The patches are a available here :
http://support.microsoft.com/kb/959209/en-us
Hope this helps 