Linq to Entities or EF version of Set Identity_Insert <TableName> ON

Similar to This Question using linq to SQL, but I don't want to just execute SQL commands from the code. I could write a stored procedure.

I am writing the year rollover functions for an application and I would like to be able to make sure that the next year uses the next available PK slot so that I can use math to go back between years.

The user wants a roll back function also, so there is the distinct possibility of gaps since a year will be deleted at that point.

This also begs the question of whether relying on pk values to be sequential is too brittle...

Question: Is there a way to s开发者_高级运维hort-circuit the way EF inserts records and specify the primary key I would like inserted with the record?

I would say your design is absolutely too brittle. The PK really should not be an application concern except for retrieving a given record, imo.

That said, if you must do it that way, you can set the StoreGeneratedPattern flag to "None" and then insert whatever PK you want to from the app, but of course if hte DB itself is using an autoincrementing key of some kind (e.g. IDENTITY), then you'll still break.

Update Why do the requirements to a) have one row per year and b) roll back each year translate into anything at all for the PK? Why not just have a 'year' column (set to UNIQUE or not) which can be used in your query?