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 this article:

pg
Pawel Gerr is architect consultant at Thinktecture. He focuses on backends with .NET Core and knows Entity Framework inside out.

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

Free
Newsletter

Current articles, screencasts and interviews by our experts

Don’t miss any content on Angular, .NET Core, Blazor, Azure, and Kubernetes and sign up for our free monthly dev newsletter.

EN Newsletter Anmeldung (#7)
Related Articles
AI
sg
One of the more pragmatic ways to get going on the current AI hype, and to get some value out of it, is by leveraging semantic search. This is, in itself, a relatively simple concept: You have a bunch of documents and want to find the correct one based on a given query. The semantic part now allows you to find the correct document based on the meaning of its contents, in contrast to simply finding words or parts of words in it like we usually do with lexical search. In our last projects, we gathered some experience with search bots, and with this article, I'd love to share our insights with you.
17.05.2024
Angular
SL-rund
If you previously wanted to integrate view transitions into your Angular application, this was only possible in a very cumbersome way that needed a lot of detailed knowledge about Angular internals. Now, Angular 17 introduced a feature to integrate the View Transition API with the router. In this two-part series, we will look at how to leverage the feature for route transitions and how we could use it for single-page animations.
15.04.2024
.NET
KP-round
.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