Lifetime of a LINQ to SQL DataContext

Microsoft news and tips » Lifetime of a LINQ to SQL DataContext

Microsoft news and tips » Lifetime of a LINQ to SQL DataContext — Mon, 28 Apr 2008 08:34:47 GMT

PingBack from http://microsoftnews.askpcdoc.com/data-access/lifetime-of-a-linq-to-sql-datacontext-2

Microsoft news and tips » Lifetime of a LINQ to SQL DataContext

Microsoft news and tips » Lifetime of a LINQ to SQL DataContext — Mon, 28 Apr 2008 08:34:47 GMT

PingBack from http://microsoftnews.askpcdoc.com/data-access/lifetime-of-a-linq-to-sql-datacontext

re: Lifetime of a LINQ to SQL DataContext

rogerj — Mon, 28 Apr 2008 17:26:46 GMT

Dinesh,

Welcome back!

--rj

re: Lifetime of a LINQ to SQL DataContext

Tim Fischer — Tue, 29 Apr 2008 17:05:17 GMT

>>Long-lived usage:DataContext does not itself overwrite the objects once you retrieve them through queries.

How would i be able to load new values into an existing object in the context, then?

Thank you

Tim

re: Lifetime of a LINQ to SQL DataContext

Dinesh.Kulkarni — Mon, 05 May 2008 03:41:23 GMT

Tim,

I am not sure about the exact scenario you are looking for. You can always load new values into your objects. It is LINQ to SQL that is careful about not overwriting objects that belong to the user.

The real question is how to get the new values to load them in your object. For that, you can also use a different DataContext instance (probably with same mapping and connection string).

The notion of "Refresh()" is an intersting and a bit involved. I will likely post about it separately.

Thanks,

Dinesh

LINQ to SQL DataContext and Ent. Framework ObjectContext Lifetime Blog posts

Hot Topics — Mon, 19 May 2008 22:42:08 GMT

Here's a collection of  posts about the lifetime of these two related contexts. From Dinesh

LINQ to SQL Tips 6: How to refresh given DataContext won't stomp on your objects

Dinesh's Cyberstation — Sat, 24 May 2008 04:16:32 GMT

The DataContext is a rather careful beast. Once an object is retrieved, the DataContext will not stomp

On LINQ to SQL, Concurrency and Timestamps

Mike Taulty's Blog — Wed, 02 Jul 2008 01:10:35 GMT

I came across a bit of a glitch in using timestamps for checking concurrency violations in LINQ to SQL...

LINQ to SQL Tips 9: Understanding DataContext's internal caching

Dinesh's Cyberstation — Wed, 02 Jul 2008 08:24:16 GMT

Back to the "tips" series after a little break ... One common question I get is about caching of data

Linq to SQL pitfalls

Willem Meints — Tue, 09 Dec 2008 22:48:02 GMT

Currently I'm hard at work on a project where we use Linq to SQL quite a lot. It has led to some interesting

Linq to Sql lifetime

Iga lahendus tekitab uusi probleeme ehk alati võib leida veel ühe bugi. — Tue, 17 Mar 2009 00:59:29 GMT

Üks teemaisd, mis mind mõnda aega on Linq to SQL juures mõtisklema pannud, on selle lifetime ehk kui