September 27, 2011 4:43 am
If you create a table with a PK that is not identity and then create a EF class from that and then try and load in an empty value, you get a System.Data.Update exception:
If you go ahead and change the server to identity without updating EF on your client, you still get a System.Data.Update exception, but with a different inner exception:
What you need to do is to fix it by changing to identity and then updating the EF on the client:
Volia: the change will now persist
However, if you create a PK on an existing table where there used to be a Implied key, you get an error. You need to drop the table and re-create.
Posted by jamie dixon
Categories: .NET 4.0: Parallelism, EF2, etc...
Tags:
Mobile Site | Full Site
Get a free blog at WordPress.com Theme: WordPress Mobile Edition by Alex King.