Book Image

Mastering Entity Framework Core 2.0

By : Prabhakaran Anbazhagan
Book Image

Mastering Entity Framework Core 2.0

By: Prabhakaran Anbazhagan

Overview of this book

Being able to create and maintain data-oriented applications has become crucial in modern programming. This is why Microsoft came up with Entity Framework so architects can optimize storage requirements while also writing efficient and maintainable application code. This book is a comprehensive guide that will show how to utilize the power of the Entity Framework to build efficient .NET Core applications. It not only teaches all the fundamentals of Entity Framework Core but also demonstrates how to use it practically so you can implement it in your software development. The book is divided into three modules. The first module focuses on building entities and relationships. Here you will also learn about different mapping techniques, which will help you choose the one best suited to your application design. Once you have understood the fundamentals of the Entity Framework, you will move on to learn about validation and querying in the second module. It will also teach you how to execute raw SQL queries and extend the Entity Framework to leverage Query Objects using the Query Object Pattern. The final module of the book focuses on performance optimization and managing the security of your application. You will learn to implement failsafe mechanisms using concurrency tokens. The book also explores row-level security and multitenant databases in detail. By the end of the book, you will be proficient in implementing Entity Framework on your .NET Core applications.
Table of Contents (20 chapters)
Title Page
Credits
About the Author
About the Reviewers
www.PacktPub.com
Customer Feedback
Dedication
Preface
4
Building Relationships – Understanding Mapping

Introducing concurrency tokens


The concurrency token would be the benchmark value used by EF to identify whether the transaction has a conflict or not. We will be exploring different types of concurrency tokens available and, if modified, how they stop the other user from updating the same.

The concept should be pretty simple, and we will keep ourselves in the shoes of the Microsoft developers and see what algorithm should be adopted for the implementation.

The following algorithm is required at the higher level:

  • The entity should identify at least one column (concurrency check column) to let's validate whether the row is updated or not
  • The identified column will be used in any update operation performed by the framework to check whether the update is valid or not:
    • The column is concluded as valid if the previous value in the updating model and the original value fed to the data store match, otherwise it would be marked as invalid
  • If the concurrency column has invalid data then an exception should...