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

Unnecessary volume returned


We have been using data luxuriously so far without keeping usage in mind. One fine example is the delete operation, which we can see in all the CRUD operations. If we take a look at the Persondelete operation, we can see that the entire Person entity was returned from the context and it was used for the deletion. The following code retrieves the Person entity and uses the entity for delete operation:

    public async Task<IActionResult> DeleteConfirmed(int id)
    {
var person = 
       await _context.People.SingleOrDefaultAsync(m => m.Id == id);
      _context.People.Remove(person);
      await _context.SaveChangesAsync();
      return RedirectToAction("Index");
    }

The pitfall for the preceding approach was, first a database call was made to retrieve the entire Person object, which is an overhead. After that, the required delete operation was performed using the Id of the person, which was available before the Person retrieval. The following screenshot...