Entity Framework auto incrementing field, that isn't the Id
Solution 1
You can annotate that property with DatabaseGenerated(DatabaseGeneratedOption.Identity)
. EF allows only single identity column per table.
public class Foo
{
[Key]
public Guid Id { get; set; }
[DatabaseGenerated(DatabaseGeneratedOption.Identity)]
public long Bar { get; set; }
}
Solution 2
Old post thought I would share what I found with Entity Framework 6.1.3.
I created a simple data layer library using C# and .NET Framework 4.6.1, added a simple repository/service class, a code first context class and pointed my web.config file to a local SQL Express 2014 database.
In the entity class I added the following attribute constructor to the Id column:
[Key]
[DatabaseGenerated(DatabaseGeneratedOption.Identity)]
public Guid Id { get; set; }
Then I created a new migration by typing the following in Visual Studio 2015 Package Manager:
Add-Migration
Give the migration a name and then wait for the DbMigtation class to be created. Edit the class and add the following CreateTable operation:
CreateTable(
"dbo.Article",
c => new
{
Id = c.Guid(nullable: false, identity: true),
Title = c.String(),
Content = c.String(),
PublishedDate = c.DateTime(nullable: false),
Author = c.String(),
CreateDate = c.DateTime(nullable: false),
})
.PrimaryKey(t => t.Id);
}
The above table is an example the key point here is the following builder annotation:
nullable: false, identity: true
This tells EF to specifiy the column as not nullabe and you want to set it as an identity column to be seeded by EF.
Run the migration again with the following command:
update-database
This will run the migration class dropping the table first (Down() method) then creating the table (Up() method).
Run your unit tests and/or connect to the database and run a select query you should see your table in its new form, add some data excluding the Id column and you should see new Guid's (or whatever data type your choose) to be generated.
Related videos on Youtube
JamesStuddart
.Net Developer and Solutions Architect Specialising in web development, but covers the spectrum of platforms with .Net Follow me on Twitter: @JamesStuddart Find me on Linked in: James Studdart Listen to my podcast: The Cynical Developer
Updated on July 09, 2022Comments
-
JamesStuddart almost 2 years
I know this isn't the most ideal solution, but I need to add an auto incrementing field to one of my EF Code First objects. This column id NOT the Id, which is a guid.
Is there anyway for me to define the auto incrementing field in code, or would creating the column myself and defining in the DB that its auto incrementing work?
-
JamesStuddart about 12 yearsI had seen the DatabaseGeneratedOption.Identity but tbh I had been lazy and hadnt read into it, I just assumed that it made that column the PKey field. Thanks, I will give it a go.
-
amd about 9 yearsIs this will still work with Multitenant Databases ?
-
Eranga about 9 years@Ahmad It will not work if each tenant has its own seed
-
Jo Smo over 8 yearsI need both to be type
int
, but it doesn`t work with your code. The Primary key is always 0. Any ideas why this is? -
Mdumanoj almost 6 yearsI have my Entity class same like this. If I try to update
Foo
Entity. I getting Error likeCannot Update Identity column Bar
. Any idea about this?