> You'll know that transactions are supported when the > src/DbLinq/Test/Providers/Transactions.cs tests are not marked > [Explicit]. (We use [Explicit] to mark tests that are known failures.)
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. Andrus. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
