Entity Framework Core 3.0 – “Hidden” GROUP BY Capabilities (Part 2)

In the previous blog post we used a navigational property to work around the limitations of the extension method GroupBy. The problem is, there is not always such a property we can use for grouping. Especially, when following domain driven design practices, a bidirectional navigation is undesirable to not to pollute the domain model (too much). Besides not introducing a navigational property intentionally there might be use cases when we have to group data by property such as the name of a record. In this case there simply cannot be a navigational property.

In diesem Artikel:

pg
Pawel Gerr ist Architekt und Consultant bei Thinktecture. Er hat sich auf .NET Core Backends spezialisiert und kennt Entity Framework von vorne bis hinten.

In this post we look at LINQ queries that behave in the same way as the navigational property we used in the previous post:

				
					var firstProducts = Context.ProductGroups  
   .Select(g => g.Products.OrderBy(p => p.Name).FirstOrDefault())  
   .ToList();
				
			

Let’s achieve the same without using the property Products. Yet again, we start from the product groups but instead of using the navigational property we use the DbSet Products. The join condition between a group and the products is specified inside of the extension method FirstOrDefault.

				
					var firstProducts = Context.ProductGroups  
   .Select(g => Context.Products  
       .OrderBy(p => p.Name)  
       .FirstOrDefault(p => p.GroupId == g.Id))  
   .ToList();
				
			

The generated SQL looks like the following:

				
					SELECT [t0].*  
FROM  
   ProductGroups AS p  
   LEFT JOIN  
   (  
      SELECT *  
      FROM  
      (  
         SELECT *, ROW_NUMBER() OVER(PARTITION BY p0.GroupId ORDER BY p0.Name) AS row  
         FROM [Products] AS [p0]  
      ) AS [t]  
      WHERE [t].[row] <= 1  
   ) AS t0 ON p.Id = t0.GroupId
				
			

The SQL statement is identical to the one that was generated when using the navigational property.

Now, imagine there is no DbSet ProductGroups and the property GroupId is just a regular property like Name. As a replacement for missing ProductGroups we use SELECT DISTINCT GroupId on the Products. The 2nd part of the query stays the same.

				
					var firstProducts = Context.Products  
   .Select(p => p.GroupId)  
   .Distinct()  
   .Select(id => Context.Products  
        .OrderBy(p => p.Name)  
        .FirstOrDefault(p => p.GroupId == id))  
   .ToList();

				
			

The generated SQL statement is:

				
					 SELECT [t1].*  
    FROM  
    (  
       SELECT DISTINCT p.GroupId  
       FROM Products AS p  
    ) AS t  
    LEFT JOIN (  
        SELECT t0.*  
        FROM (  
            SELECT p0.*, ROW_NUMBER() OVER(PARTITION BY p0.GroupId ORDER BY p0.Name) AS row  
            FROM Products AS p0  
        ) AS t0  
        WHERE t0.row <= 1  
    ) AS t1 ON t.GroupId = t1.GroupId
				
			

For grouping of data using built-in capabilities of Entity Framework Core 3.0 should be enough for most cases. For more advanced use cases we can’t do much but extending EF with custom functionality.

Demos: NavigationPropertiesAlternativeQueriesDemo.cs

Kostenloser
Newsletter

Aktuelle Artikel, Screencasts, Webinare und Interviews unserer Experten für Sie

Verpassen Sie keine Inhalte zu Angular, .NET Core, Blazor, Azure und Kubernetes und melden Sie sich zu unserem kostenlosen monatlichen Dev-Newsletter an.

Newsletter Anmeldung
Diese Artikel könnten Sie interessieren
Database Access with Sessions
.NET
KP-round

Data Access in .NET Native AOT with Sessions

.NET 8 brings Native AOT to ASP.NET Core, but many frameworks and libraries rely on unbound reflection internally and thus cannot support this scenario yet. This is true for ORMs, too: EF Core and Dapper will only bring full support for Native AOT in later releases. In this post, we will implement a database access layer with Sessions using the Humble Object pattern to get a similar developer experience. We will use Npgsql as a plain ADO.NET provider targeting PostgreSQL.
15.11.2023
Old computer with native code
.NET
KP-round

Native AOT with ASP.NET Core – Overview

Originally introduced in .NET 7, Native AOT can be used with ASP.NET Core in the upcoming .NET 8 release. In this post, we look at the benefits and drawbacks from a general perspective and perform measurements to quantify the improvements on different platforms.
02.11.2023
.NET
KP-round

Optimize ASP.NET Core memory with DATAS

.NET 8 introduces a new Garbage Collector feature called DATAS for Server GC mode - let's make some benchmarks and check how it fits into the big picture.
09.10.2023
.NET CORE
pg

Incremental Roslyn Source Generators: High-Level API – ForAttributeWithMetadataName – Part 8

With the version 4.3.1 of Microsoft.CodeAnalysis.* Roslyn provides a new high-level API - the method "ForAttributeWithMetadataName". Although it is just 1 method, still, it addresses one of the biggest performance issue with Source Generators.
16.05.2023
AI
favicon

Integrating AI Power into Your .NET Applications with the Semantic Kernel Toolkit – an Early View

With the rise of powerful AI models and services, questions come up on how to integrate those into our applications and make reasonable use of them. While other languages like Python already have popular and feature-rich libraries like LangChain, we are missing these in .NET and C#. But there is a new kid on the block that might change this situation. Welcome Semantic Kernel by Microsoft!
03.05.2023
.NET
sg

.NET 7 Performance: Regular Expressions – Part 2

There is this popular quote by Jamie Zawinski: Some people, when confronted with a problem, think "I know, I'll use regular expressions." Now they have two problems."

In this second article of our short performance series, we want to look at the latter one of those problems.
25.04.2023