In Entity Framework Core 3 (EF 3) the SQL statement generation (re)introduced the Cartesian Explosion problem. A lot has happened since then, so it is time to revisit the issue with Entity Framework Core 7 (EF 7).
Kategorie: Entity Framework
The N+1 queries problem has been our constant companion since day one of Entity Framework (Core). Entity Framework Core 2 (EF 2) introduced a new feature that caused the „N+1 queries problem“ more often and was more difficult to detect, so it was removed in the following version. After a little back and forth, let’s see how Entity Framework Core 7 (EF 7) handles this issue and why it will likely remain in the future.
The requirement to store additional fields, unknown at development time, in a relational database is not new. Nonetheless, none of the projects I know of are willing to change the database structure at runtime. What if there is a project which needs dynamically created fields and doesn’t want or cannot use entity–attribute–value model or switch to No-SQL databases?