Query: Collection projection identifier in different order during set operation

Open
#24,475 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp
Domain
database

Research direction

Start by locating the query translation code that matches collection projection identifiers during set operations, then trace the join scenario described in the issue. The work is done when differing identifier order is accepted only when identifiers from both sides are used and their value comparers match, while the described query can translate.

Written by the indexing model from the issue text.

Description

area-query

Currently we match the ordering of collection projection identifiers during set operation.
We could relax this criteria to allow more query translation. We would need to make sure that identifiers from both are used and they both have same value comparers.

Scenarios of query,
when generating join between 2 entities - if the join is performed in reverse order in right side of set operation (but generated result would be anonymous type which would be same in both), following by selecting a collection over it.

Dominant language
C#
Stars
14.8k
Forks
3.4k
Avg merge
2d 5h
Merged PRs (30d)
134

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dotnet/efcore

All issues in dotnet/efcore

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.