Re: LINQ for SQL Conflict Resolution

Thanks Peter, but unfortunately that doesn't help. That page tells you how to prevent LINQ checking that individual fields haven't changed. However, I find that even if I remove checking on every individual field, DataContext.SubmitChanges() still throws an exception because the entire row has been deleted - I don't want it to do that because that's just the trigger acting on the Delete-This-Row flag having been set. 

(Besides, I'd slightly prefer it if individual field checking was left on. An error in an individual field would likely indicate a genuine concurrency issue)

Simon


On Wed, 1 Apr 2009 14:44:33 -0400, Peter Ritchie <[email protected]> wrote:

>I think you want to have a look at this MSDN page:
>http://msdn.microsoft.com/en-us/library/bb399394.aspx
>
>===================================
>View archives and manage your subscription(s) at http://peach.ease.lsoft.com/archives

===================================
View archives and manage your subscription(s) at http://peach.ease.lsoft.com/archives