Re: Update
Posted by:
schizoid
Date: August 06, 2006 10:08AM
Hey Dan,
I have been using TransactionScope with ADO.NET 2.0 exactly as you mentioned, in so much as rolling back transactions amounted to not calling scope.Complete (e.g. if an exception is thrown).
Now, recently I tried moving to MySQL, and ran into the *exact* same issue as you. I wanted to migrate from SQL Server *to* MySQL, and I really can't. It's infeasible for me to make the change that you did since if I ever need to go back to SQL Server, then I won't be getting the benefits of TransactionScope.
I really think that MySQL needs to fix this issue to get more people using MySQL underneath .NET 2.0 apps. I would say this is of critical importance. For now, I will continue using SQL Server.
Kevin
Subject
Written By
Posted
Re: Update
August 06, 2006 10:08AM
September 20, 2006 11:29AM
September 26, 2006 08:02AM
September 28, 2006 06:51PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.