Just sharing some of my inconsequential lunch conversations with you... RSS  

Monday, October 27, 2008

LINQ 'Row not found or changed'

This was pretty annoying... after a while getting an unexpected 'Row not found or changed', here's the solution:

disabled concurrency checks on *all* fields, then added them back one at a time.  Turns out the culprit was a string field that was nullable in the DB but not set as nullable in the designer.

Should probably have chosen EF. No comments...

1 comment:

orangeeli said...

Hey Mario. Had the same problem. Check out this post on LINQ to SQL funeral. http://codebetter.com/blogs/david.hayden/archive/2008/10/31/linq-to-sql-is-dead-read-between-the-lines.aspx


eliseu martinho

Development Catharsis :: Copyright 2006 Mário Romano