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:
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
Cheers,
eliseu martinho
Post a Comment