By dcompiled

2010-06-10 05:05:39 8 Comments

I want to loop through a collection of objects and add them all to a table. The destination table has an auto-increment field. If I add a single object there is no problem. If I add two objects both with the primary key of zero, the entity framework fails. I can manually specify primary keys but the whole point of trying the EF was to make life easier not more complicated. Here is the code and the exception received follows.

foreach (Contact contact in contacts)
    Instructor instructor = InstructorFromContact(contact);             

catch (Exception ex)

The error is:

System.InvalidOperationException: The changes to the database were committed successfully, but an error occurred while updating the object context. The ObjectContext might be in an inconsistent state. Inner exception message: AcceptChanges cannot continue because the object's key values conflict with another object in the ObjectStateManager. Make sure that the key values are unique before calling AcceptChanges. at System.Data.Objects.ObjectContext.SaveChanges(SaveOptions options)
at System.Data.Objects.ObjectContext.SaveChanges() at DataMigration.Program.CopyInstructors() in C:\Projects\DataMigration\Program.cs:line 52


@yu yang Jian 2017-04-14 09:20:05

I'm using EF6, to set the StoreGeneratedPattern, you can also try open EDMX file in Visual Studio, right click on the Data Column in table and select Properties,

Then you can set it from None to Identity in Properties Window:

@cepriego 2010-06-14 14:59:28

This happens because despite the auto-generated value of the column was created in the Database the EF never knew about it.

So, in order to inform EF that the DB will handle the generated value you have to to open your edmx file (I always use the XML editor of VS to do this) and in the store schema definition language (SSDL) area, add the attribute StoreGeneratedPattern="Identity" to the column that needs the generated pattern. In this way EF reads the value generated in the DB and stores it in memory cache.

Your entity type definition will look more or less like this:

 <EntityType Name="INVOICE">
            <PropertyRef Name="CODE" />
          <Property Name="CODE" Type="varchar" Nullable="false"
              MaxLength="10" StoreGeneratedPattern="Identity"/>                 

Be aware that if you happen to update your model all these changes will be lost and you'll have to repeat all the entire process.

This works for EF 1.0, I'm not sure if in EF4 all these issues are already fixed.

@dcompiled 2010-06-14 19:02:25

I think where I went wrong is in that I initially created the model from the database and forgot to set the autonumber field. LaterI edited my database and set this property followed by the "update model from database" command within visual studio 2010. The update feature seems to add new properties but not exactly sure if it 'fixes' existing modified properties correctly. By deleting my model and recreating from scratch, the autonumber feature worked as expected. However had I known better, I would have tried your idea.

@cepriego 2010-06-15 09:08:43

Currently (but hopefully soon!) I'm not using EF4, however I read something in this page that talks about this:‌​dl

@kimsk 2012-07-06 20:24:02

Microsoft provides a hotfix here for VS2010SP1.… It seems to work for me.

@AlexGH 2019-08-02 20:06:53

@kimsk The link doesn't work anymore. What do I need to download?

@Devart 2010-06-10 08:15:59

Set the StoreGeneratedPattern attribute to "Identity" in your SSDL for the autoincrement field. It should help.

@DanO 2010-07-21 21:57:18

Note that you can't just set this property in the designer, you have to edit the SSDL section by hand. I read past this answer and thought: "I've already done that.", and I kept looking, I could have save hours by noticing the SSDL This is a know bug in the designer.‌​dl and‌​ork/…

@smartcaveman 2011-03-10 23:46:45

you may want to weigh in on this:…

@as-cii 2012-12-11 12:45:34

we are starting a new MVC 4 project using VS2012, EF 5 and ODP.NET for Oracle 11 and we are experiencing exactly the same problem. Everytime we "generate database from model", the ssdl part on edmx file loses the "storedGeneratedPatter=Identity" attribute. Does anybody know any hotfix for VS2012 and EF 5 supporting Oracle too?

Related Questions

Sponsored Content

29 Answered Questions

[SOLVED] Fastest Way of Inserting in Entity Framework

7 Answered Questions

[SOLVED] Entity Framework 5 Updating a Record

16 Answered Questions

[SOLVED] Entity Framework vs LINQ to SQL

1 Answered Questions

[SOLVED] Entity Framework TPC: Why does BaseEntity Id need to be of type Guid?

1 Answered Questions

2 Answered Questions

[SOLVED] Inconsistent Object State Error In Entity Framework When Saving

2 Answered Questions

1 Answered Questions

[SOLVED] Entity Framework's TPC mapping results in error

Sponsored Content