Question

I have the following code in my context, and no explicit table-class mapping, yet my database keeps getting created (by my DropCreateDatabaseIfModelChanges initializer) with an EmployeeStatus table, not EmployeeStatuses. Is there a known issue with this, or am I going insane or what?

    public DbSet<Department> Departments { get; set; }
    public DbSet<EmployeeStatus> EmployeeStatuses { get; set; }

All my other tables are named exactly after their DbSet names, as I expect.

Answer 1

Entity Framework uses its pluralization service to infer database table names based on
the class names in the model—Destination becomes Destinations, Person becomes
People, etc. By convention, Code First will do its best to pluralize the class name and use the results as the name of the table. However, it might not be the same as your
table naming conventions.

You can use the Table Data Annotation to ensure that Code First maps your class to
the correct table name.