[Bug] - [Required] attribute ignored when creating column named Id

When creating a new database using EnsureCreated(), a column with the name Id is created as nullable even though the required attribute is placed on the property. I believe this is due to it being in a derived class with the Primary Key annotated in the base class. Perhaps the order of property evaluation affects the outcome.

  public class MyBaseClass
    {
        [Key]
        public int MyKey { get; set; }
    }

    [Table("Test")]
    public class MyDerivedClass : MyBaseClass, IEntityTypeConfiguration<MyDerivedClass>
    {
        [Required]
        public string Id { get; set; }

        
        void IEntityTypeConfiguration<MyDerivedClass>.Configure(EntityTypeBuilder<MyDerivedClass> builder)
        {
            _ = builder.HasKey(x => x.MyKey);
            _ = builder.HasIndex(x => x.Id).IsUnique();
        }
    }

With the above definition, a table is created with an auto-generated primary key “MyKey” and a nullable column “Id”

[roji]

@omnilogix as a workaround, you can either change the order of the properties as you’ve done, or change the name of the Id property, this way EF doesn’t initially configure it as the key by convention.

[ajcvickers]

HasBaseType should not be needed in this case. Just don’t include the base type in the model. Typical ways the base type is included in the model:

• Having a DbSet property for the type
• Having a call to ModelBuilder.Entity for the type
• Having an IEntityTypeConfiguration for the type
• Referencing it from another type in the model

Since there isn’t full repro code here I can’t tell which of these is being used. If you are not doing any of these things and the type is still included, then please attach a small, runnable project or post a small, runnable code listing that reproduces what you are seeing so that we can investigate.