LINQ to SQL : Using Transaction

Noticias externas — Tue, 07 Aug 2007 01:11:49 GMT

LINQ to SQL uses optimistic concurrency be default. LINQ to SQL is pure in memory operation, because

re: LINQ to SQL : Using Transaction

Des — Tue, 07 Aug 2007 02:47:34 GMT

I'm sure TransactionScope was introduced in .NET 2.0 not 3.0

re: LINQ to SQL : Using Transaction

wriju — Tue, 07 Aug 2007 21:23:30 GMT

Hi Des,

Thanks for correcting me. I have changed.

Wriju

re: LINQ to SQL : Using Transaction

Sam — Fri, 01 Feb 2008 06:01:12 GMT

Don't know if you resolved this issue - but try wrapping the transaction scope just around the

db.SubmitChanges();

statement and see if it works.

re: LINQ to SQL : Using Transaction

Daryl — Fri, 01 Feb 2008 13:09:55 GMT

Have I missed the point here the only difference seems to be the error message!

re: LINQ to SQL : Using Transaction

SoftParts — Sat, 02 Feb 2008 04:00:14 GMT

Seems to me the only difference is the error message!

Pessimistic would do a 'Select for update' and tell you at that point if you can't get the row which to my of thinking was necessary with databases that don't support transactions. (Old school!)

Daryl

re: LINQ to SQL : Using Transaction

Emil — Sat, 29 Mar 2008 08:31:55 GMT

It seems like TransactionScope is not used by LINQ. If you remove the ts.Complete() statement, the changed are not rolled back.

re: LINQ to SQL : Using Transaction

Emil — Sat, 29 Mar 2008 09:15:51 GMT

The reason it was not working for me was because I was using what VS2008 calls a "Local Database", i.e. SQL Server Compact Edition. Apperantly System.Transaction does not work with the Compact Edition. This is probably due to the fact that the Compact Edition does not support nested transactions.

re: LINQ to SQL : Using Transaction

Michael.Piccolo — Fri, 04 Apr 2008 19:25:01 GMT

I have created a custom BaseDataContext that facilitates setting IsolationLevels for Transactions.

re: LINQ to SQL : Using Transaction

Tersius — Tue, 27 May 2008 12:56:03 GMT

How can you handle deletes that fail due to referential integrity? It seems there is no way to undo deleteonsubmit calls.

What is LINQ? LINQ Developer Resources

DotNetJaps — Thu, 31 Jul 2008 09:05:01 GMT

LINQ is Language Integrated query. It is a integral part of visual studio 2008 and Microsoft .NET Framework

re: LINQ to SQL : Using Transaction

Richard Murillo — Thu, 21 Aug 2008 03:29:12 GMT

To Tersius:

You can use a call to InsertOnSubmit to compensate for the delete

re: LINQ to SQL : Using Transaction

mknopf — Wed, 14 Jan 2009 21:06:33 GMT

IMPORTANT: to use using TransactionScope you need to add a Reference in your project to System.Transactions, while this would seem obvious it actually isn't and is worth noting

re: LINQ to SQL : Using Transaction

Jon — Sun, 08 Feb 2009 01:01:36 GMT

So my question is on a sql database that does support transactions, will the transaction scope work?