Entity Framework Core Database first sets property nullable

Question

Iam working with Entity Framework Core and a legacy database.

When migrating the database to my models, Iam using this script:

Scaffold-DbContext "Server=abc\SQLEXPRESS;Database=mydatabase;Trusted_Connection=True;" Microsoft.EntityFrameworkCore.SqlServer -OutputDir Models

Everything works fine but the script is creating a class with a property that is nullable:

public bool? Active { get; set; }

But my database has a field, which is "Not Null"

The migration script is also creating a context file:

entity.Property(e => e.Active)
                    .IsRequired()
                    .HasColumnName("active")
                    .HasDefaultValueSql("((1))");

Why is the migrated field "Active" a nullable bool? and not just a bool in my C# models?

acinace · Accepted Answer · 2022-09-27 07:29:34Z

2

I think it's because you have a default value. In this case, EF accepts null value because the DB server puts the default one. In my experience, "Not null" field without default value render non nullable bool field in my model.

edited Sep 27, 2022 at 7:29

answered Sep 27, 2022 at 7:23

acinace

1135 bronze badges

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

1 Comment

HermanTheGerman Over a year ago

Jep, this is the reason

Collectives™ on Stack Overflow

Entity Framework Core Database first sets property 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