InMemory: Defining query should throw error for non-LINQ queryable operators

Open
#21,830 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

No files, tests, or entry points are named. Start by locating InMemory defining-query handling and inspect how query operators such as AsNoTracking and Include are processed. Done means non-LINQ queryable operators used inside a defining query produce an error, with coverage for the stated examples.

Written by the indexing model from the issue text.

Description

area-query customer-reported

e.g. AsNoTracking/Include etc.

Defining query will take ValueBuffers of Tables and generate a valueBuffer which provides values for given entitytype to make it truly server side view for InMemory.
Since non-LINQ operators has no server side equivalent, we should throw if it used inside defining query.

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.