-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Group by with projection (without aggregate) #23439
Labels
closed-out-of-scope
This is not something that will be fixed/implemented and the issue is closed.
customer-reported
Comments
/cc @smitpatel |
Duplicate of #19929 |
This is closed as a duplicate of #19929, but still fails with EF7 RC2:
|
Only final |
ajcvickers
added
closed-out-of-scope
This is not something that will be fixed/implemented and the issue is closed.
and removed
closed-duplicate
labels
Sep 27, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
closed-out-of-scope
This is not something that will be fixed/implemented and the issue is closed.
customer-reported
Group by with projection
Group by (that works in Entity Framework), does not work in EF Core:
Simplest repro code
Ultimately I understand that this is mostly a client side projection, not actually group by in database. The reason why it's interesting is that it enables combining db queries and client-side projections (that seems supported by EF) in one linq statement, with complex inner filters & joins as below:
Real world use case example
Error
(from the repro example)
'Processing of the LINQ expression 'GroupByShaperExpression:
KeySelector: new {
Type = d.Type,
IsAlias = d.IsAlias
},
ElementSelector:EntityShaperExpression:
EntityType: Driver
ValueBufferExpression:
ProjectionBindingExpression: EmptyProjectionMember
IsNullable: False
' by 'RelationalProjectionBindingExpressionVisitor' failed
Include provider and version information
EF Core version:
5.0.0
Database provider: (e.g. Microsoft.EntityFrameworkCore.SqlServer)
Target framework: .NET 5.0
Operating system:
IDE: Visual Studio 2019 16.8
Bug / Feature Request?
Is this meant to work in EF Core (i.e. a bug)?
Or do I just need to tweak EF Core settings for this to work?
Or are similar linq statements not planned to be supported in EF Core?
As a side note, I could not find any guide on differences between EF and EF Core - example queries that used to work and now they don't. Any tips?
The official guide seems to ignore the (for me shocking) lack of support for LINQ statements that used to work in EF and are not working/supported in EF Core. Reading the guide one gets the impression that these frameworks are very close to feature parity.
Regards,
Stefan
The text was updated successfully, but these errors were encountered: