Entity Framework Primary/Foreign constraint name

Question

Is there any way to rename a primary/foreign key constraint name through either data annotations or fluent API?

I'm not talking about the property/column name. The constraint name. I did some search and didn't find any solutions yet.

Please help!

You can do this in an `Up` [migration](http://stackoverflow.com/a/17929867/314291) — StuartLC, Nov 12 '15 at 06:07
Yeah. I know. But is that the only way? I mean there's gotta be some way through fluent API when defining primary keys right? — renjith, Nov 12 '15 at 06:08
Seemingly you can also go as far as [overriding the SqlGenerator conventions](http://stackoverflow.com/a/31553476/314291) — StuartLC, Nov 12 '15 at 06:10
@StuartLC thanks! That'll work, although that's a bit code overload. I was hoping for a simple solution. Migration is the way..! — renjith, Nov 12 '15 at 06:19

score 1 · Answer 1 · answered Jun 20 '18 at 20:24

1

with .HasConstraintName like you can see in the underlying example

entity.HasOne(d => d.Director)
                    .WithMany(p => p.Movie)
                    .HasForeignKey(d => d.DirectorId)
                    .OnDelete(DeleteBehavior.ClientSetNull)
                    .HasConstraintName("FK_Movie_Person");

answered Jun 20 '18 at 20:24

Nick

11
1

is it possible with EF6? – Pishang Ujeniya Jan 04 '21 at 08:26

score -1 · Answer 2 · edited May 23 '17 at 12:24

It's not possible to customize the foreign key constraint name with Data annotations or Fluent API.

There is some options that you can follow:

Implement a custom sql generator class derived from SqlServerMigrationSqlGenerator from System.Data.Entity.SqlServer
When the tables get created via migrations, the migration code that gets automatically generated, so you can set a custom constraint name(s)
When the tables already exist you can drop the constraint and add a new renamed one in a migration

Entity Framework Primary/Foreign constraint name

2 Answers2