Thank you Pascal for your interest. For what I've seen, DataContext.Transaction property is not used anywhere and a new transaction is always created on SubmitChanges, but I can be wrong. Started to use dblinq just a few weeks ago on a project prototype, so I'm still learning its code base.
Pedro On Wed, Nov 5, 2008 at 9:10 PM, Pascal Craponne <[EMAIL PROTECTED]> wrote: > Hi Pedro, > > I also noticed some strange code related to transactions in DbLinq, I'll > probably need to take a look at it soon. I'll let you know here when the > problem is fixed. > > Pascal. > > On Wed, Nov 5, 2008 at 19:40, Pedro Ferreira <[EMAIL PROTECTED]> > wrote: >> >> Hi, I'm sorry if this has been asked or if I'm doing something wrong, >> but I've searched around and couldn't find anything. >> >> Does dblinq supports using an existing transaction on DataContext for >> its SubmitChanges method? >> >> I'm using the Oracle provider (with Oracle 10g Enterprise) and >> although I set the DataContext.Transaction property to an already >> created transaction, it appears that a new transaction is always >> initiated, as I get an exception saying that parallel transactions are >> not supported on OracleClient. >> >> Thanks, >> >> Pedro >> >> > > > > -- > Pascal. > > jabber/gtalk: [EMAIL PROTECTED] > msn: [EMAIL PROTECTED] > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
