Query: we can uniquely identify keyless entities that have Distinct operation applied on them
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
The issue does not name specific files or tests. Start by locating the Distinct/GroupBy identifier-salvage logic in EF Core's query processing and review issue #26077 for the complex-expression limitation. Done means keyless entities in nested collection queries can use a distinct projection for result bucketing without the current missing-identifier failure.
Written by the indexing model from the issue text.
Description
Currently we have logic for Distinct/GroupBy to "salvage" identifiers, in case they are not part of the distinct projection / grouping key. In case of Distinct we simply can use the entire projection (unless it contains some complex expressions, see https://github.com/dotnet/efcore/issues/26077), since it's now guaranteed to be unique, and in case of group by we use entire grouping key.
We should also be able to do this for keyless entities - they don't have identifiers so anytime we have a nested collection scenario involving them, we throw due to lack of identifiers needed to perform correct bucketing of the results. For now, we only do this trick if there were any identifiers to begin with.
- Dominant language
- C#
- Stars
- 14.8k
- Forks
- 3.4k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 134
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dotnet/efcore
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
customer-reported
Difficulty 5/5 Over a week Newbie friendliness 38/100
-
area-cosmos area-vector-search
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
area-cosmos
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
area-tools needs-design
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
:watch: Not Triaged 11.0 fundamentals/subsvc
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
dotnet/AspNetCore.Docs#37699 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SubtitleEdit/subtitleedit#15108 · 1 comment ·
-
area/docs-content Bug pulumi/docs
Difficulty 1/5 1-3 hours Newbie friendliness 94/100
-
agentic-workflows untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 76/100