Query: investigate support for custom table sources

Open
#26,563 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp
Domain
backend, databases

Research direction

Start by tracing how tableexpression, joinexpression(base), selectexpression, and fromsql expressions are handled, then examine SharedTypeEntityExpandingExpressionVisitor. Determine whether providers need custom table sources and which provider-specific extensibility hooks are required. Done means an agreed design or implementation scope for that provider support, with affected query behavior identified.

Written by the indexing model from the issue text.

Description

area-query needs-design

Currently we have tableexpression, joinexpression(base), selectexpression, fromsql expression as table sources. They sometimes require custom logic to extract the correct tableexpressionbase from the given expression (e,g, SelectExpression may contain multiple tables and we maintain mapping of which projection maps to which table underneath) - we should investigate if we want to allow for custom table sources on the provider, and what extensibility hooks we need to provide (e.g. SharedTypeEntityExpandingExpressionVisitor might need a provider specific hook)

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.