Entity Framework Creates Plural Table Names, But My View Expects a Singular Name: What Went Wrong?

Entity Framework Creates Plural Table Names, but View Expects a Singular Table Name

In this scenario, Entity Framework is configured to implement a code-first approach, creating the database based on the model classes. However, a discrepancy arises between the pluralized table name generated by Entity Framework and the singular table name expected by the strongly typed view.

Initially, pluralization of table names was enabled in EF, resulting in the creation of the 'votes' table in the database. However, the view raised an exception, seeking the table named 'vote'.

To resolve this discrepancy, several adjustments were made:

• Application Start Method: A correction was made in the Application Start method to initialize the database using myDBInitializer() instead of DropCreateDatabaseAlways().
• OnModelCreating Method: The call to the base implementation of OnModelCreating was removed, and the PluralizingTableNameConvention was excluded from the conventions in the model builder.
• Database Creation: It was discovered that MySQL .net Connector 6.4.4 allows EF to create databases. Therefore, having an existing blank database was unnecessary.

After these changes were implemented, the database was properly created, and the view successfully accessed the data from the pluralized 'votes' table.

Despite the resolution, the root cause of the singular/plural discrepancy remains unclear. However, this workaround allows for further progress in developing the application.

The above is the detailed content of Entity Framework Creates Plural Table Names, But My View Expects a Singular Name: What Went Wrong?. For more information, please follow other related articles on the PHP Chinese website!