...
On Wed, 2009-09-16 at 16:03 +0300, Andrus wrote:
> Will the following workaround work when previous message method need to be
> called multiple times in single transaction or is there something better:
>
> 1. Open connection manually and start transaction in this connection.
> 2. Pass this connection to DataContext constructor
> 3. Change DbLinq SubmitChanges not to call start transaction and commit
> methods.
> 4. Call method from previous message for all entity sets which needs to be
> changed.
> 5. Call Commit manually
> 6. Dispose opened connection.
We're attempting to mimic the .NET API, which documents [0]:
In a System.Transactions transaction, a DataContext will not
open or close a connection to avoid promotion.
Thus your manual workaround should continue to work (otherwise it's a
bug in DbLinq, or I'm completely confusing things).
- Jon
[0] http://msdn.microsoft.com/en-us/library/bb292288.aspx
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"DbLinq" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/dblinq?hl=en
-~----------~----~----~----~------~----~------~--~---
