Mapping to Your Database is a Private Affair
Your mapping to your database is generally coupled to the design of the data and the mapping provider’s ability to implement a relational or non-relational model. This means your ORM influences the design of your mapped classes and/or the design of system that uses these mapped classes. i.e. your design can be limited in certain aspects by how the mapper is implemented. Because of these idiosyncrasies, your choice of ORM becomes an implementation detail; so, you want to keep any of its details and generated classes out of your interfaces. You want to keep your ORM’s classes and the classes … Continue reading Mapping to Your Database is a Private Affair