Discussion on: LINQ to SQL and the quest for the perfect DataContext “lifetime” http://itknowledgeexchange.techtarget.com/serviceendpoint/linq-to-sql-and-the-quest-for-the-perfect-datacontext-lifetime/ Yet another destination in a service-oriented world Sun, 12 Oct 2008 00:19:03 +0000 http://wordpress.org/?v=wordpress-mu-1.2.1 By: Quango http://itknowledgeexchange.techtarget.com/serviceendpoint/linq-to-sql-and-the-quest-for-the-perfect-datacontext-lifetime/#comment-67 Quango Fri, 26 Sep 2008 09:52:01 +0000 http://itknowledgeexchange.techtarget.com/serviceendpoint/linq-to-sql-and-the-quest-for-the-perfect-datacontext-lifetime/#comment-67 Let's look at your WinForms approach. One datacontext - great for cacheing static data like a list products. Forms are databound to the objects retrieved via LINQ. User opens Form A to edit some data on Table A.. is half way through editing and gets a phone call - can you change something on Table B. So opens Form B and edits the data, clicks save, which calls our .SubmitChanges. Oh dear - one datacontext - one operation - she's saved edits on A and B and now A is modified even though she didn't want to do that. Let’s look at your WinForms approach. One datacontext - great for cacheing static data like a list products. Forms are databound to the objects retrieved via LINQ.

User opens Form A to edit some data on Table A.. is half way through editing and gets a phone call - can you change something on Table B.

So opens Form B and edits the data, clicks save, which calls our .SubmitChanges. Oh dear - one datacontext - one operation - she’s saved edits on A and B and now A is modified even though she didn’t want to do that.

]]>