Going one step further from private properties, in a well-defined model, it may make sense to hide certain properties from the developers so that they do not make unwanted changes to them, consciously or not.
Historically, Entity Framework, like most ORMs, has three models:
- POCO model: This represents the .NET classes and their properties and references
- Database model: This represents the tables, views, and columns (in the case of relational data stores) where data is actually stored
- Mapping model: This model binds the two preceding models; this is where we say that the
MyEntityclass is to be stored in the
MY_ENTITYtable and the
Idproperty goes into the
Entity Framework used to call these models Conceptual ...