ChangeConflictException in UPDATE
25.08.2009 Вторник 17:21
Context: LINQ-to-SQL
Symptoms:
ChangeConflictException while doing UPDATE:
Row not found or changed
OR
1 of 2 updated failed
If you look into the SQL Server profiler you see a weird UPDATE statement ending with "WHERE 0 = 1".
Cause:
Most often these errors are caused by a mismatch between the database and the LINQ-to-SQL data model representation of the database.