You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using EntityFrameworkCore we can map an entity to multiple tables or multiple entities to a single table (TPT, TPH etc)
This made me wonder about the usage of nouns like “table” and “column” (when configuring IncludeTable/ExcludeTable). Perhaps a better and more consistent fit with EFCore domain language would be “entity” (or “entity type”) and “property”.
Hence IncludeEntity/ExcludeEntity instead…?
There is not always a one to one mapping regards entity to table.
The text was updated successfully, but these errors were encountered:
I'm not sold on this, as I think there are other storage shapes like Collection and Fields for other NoSQL storage types when we think of the repository pattern features.
Yes, the two configs should be merged and I think a future move towards a simple API that defines the storage mechanism as a Repository, EF Context, some other database provider, a JSON file, or some other format is a welcome change
Using EntityFrameworkCore we can map an entity to multiple tables or multiple entities to a single table (TPT, TPH etc)
This made me wonder about the usage of nouns like “table” and “column” (when configuring IncludeTable/ExcludeTable). Perhaps a better and more consistent fit with EFCore domain language would be “entity” (or “entity type”) and “property”.
Hence IncludeEntity/ExcludeEntity instead…?
There is not always a one to one mapping regards entity to table.
The text was updated successfully, but these errors were encountered: