Attaching an entity of type 'common.dal.tablename' failed because another entity of the same type already has the same primary key value. this can happen when using the 'attach' method or setting the state of an entity to 'unchanged' or 'modified' if any entities in the graph have conflicting key values.. Updating primary key columns is not a good practice. it confuses ef because it changes the identity of the object, and makes keeping the in-memory copy and the in-database copy of the data in sync very problematic.. In a c# 2010 application that i am working on, i want to use linq to sql to update 2 tables in a sql server 2008 database. i want to do the following: create new table1 object ; insertonsubmit(tbl1) **table 1 will contain the primary key. create new table2 object; table2 will contain a foreign key column that refers to primary key in table1 object..
Linq to sql does not come with a function like .delete(id) which allows you to delete an entity using it’s primary key. you have to first get the object that you want to delete and then call .deleteonsubmit(obj) to queue it for delete.. I am new to asp.net, c# and sql and could use some guidance.. i am using the :below: db with the linq-to-entities framework. i need to associate a particular 'ride' with a particular 'vehicle' but am unsure exactly how to proceed.. One thing to mention, if no primary key defined, ef will automatically mark all the non-nullable properties as the entity key. after we “update model from database…”, we need to set certain properties’ entity key to false if they are not primary keys..
0 comments:
Post a Comment
Note: Only a member of this blog may post a comment.