Book Image

Entity Framework Core Cookbook - Second Edition

By : Ricardo Peres
Book Image

Entity Framework Core Cookbook - Second Edition

By: Ricardo Peres

Overview of this book

Entity Framework is a highly recommended Object Relation Mapping tool used to build complex systems. In order to survive in this growing market, the knowledge of a framework that helps provide easy access to databases, that is, Entity Framework has become a necessity. This book will provide .NET developers with this knowledge and guide them through working efficiently with data using Entity Framework Core. You will start off by learning how to efficiently use Entity Framework in practical situations. You will gain a deep understanding of mapping properties and find out how to handle validation in Entity Framework. The book will then explain how to work with transactions and stored procedures along with improving Entity Framework using query libraries. Moving on, you will learn to improve complex query scenarios and implement transaction and concurrency control. You will then be taught to improve and develop Entity Framework in complex business scenarios. With the concluding chapter on performance and scalability, this book will get you ready to use Entity Framework proficiently.
Table of Contents (15 chapters)
Entity Framework Core Cookbook - Second Edition
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface
Index

Shadow properties


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 MyEntity class is to be stored in the MY_ENTITY table and the Id property goes into the MY_ENTITY_ID column

Note

Entity Framework used to call these models Conceptual Model, Storage Model, and Mapping Model. If you are curious, refer to the following link:

https://msdn.microsoft.com/en-us/data/jj650889.

So, what we are looking for is a way to have a backing data store for entities and properties that does not...