Entity Framework setting FK to nullable

Question

I'm using code first with migrations to build and keep changes to the db in sync.

If there is a class Person that has a property that points to a class FavoriteColor the db schema that gets created is a Person table with a FK called FavoriteColor_Id which is non-nullable.

I need to have that column allow nulls since Person may or may not have a favorite color.

Thx

Kirby · Accepted Answer · 2013-11-07 14:20:11Z

1

Ok once again with a good nights sleep I came in to work fresh and was able to tackle this in minutes.

Basically what had happened is that I was expecting that I would change my model class and a nice new migration cs file would be generated for me. There was no change to make to the model class since EF had auto generated this FK for me originally. I then realized that I could still run add-migration from the package manager console and it would create a new file for me where I could add my own code. I also needed to understand the difference between the Up() and Down() method. Sometimes you take these things for granted when everything is auto generated for you.

Here is what solved my issue:

public override void Up()
{
    AlterColumn("dbo.Person", "FavoriteColor_Id", c => c.Int(nullable: true));
}

answered Nov 7, 2013 at 14:20

Kirby

1,7391 gold badge17 silver badges23 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Kirby Over a year ago

When setting configurations with the Fluent API (or with decorating classes with DataAnnotations) the changes will be picked up when you add a new migration. Then all you have to do is call update-database.

Collectives™ on Stack Overflow

Entity Framework setting FK to nullable

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related