dotnet/efcore

Provide EF.Functions translations for JSON functions

Open

#29,306 opened on Oct 10, 2022

View on GitHub
 (8 comments) (16 reactions) (0 assignees)C# (14,651 stars) (3,376 forks)batch import
area-jsonarea-queryarea-sqlitearea-sqlservercustomer-reportedgood first issue

Description

For users using JSON without a strongly-typed schema, mapping the column as a string is the only option at the moment. We should provide translations for JSON_VALUE/JSON_QUERY for SQL Server and json_extract for SQLite.

Contributor guide

Tech stack
csharpsqlsqlite
Domain
backenddatabase
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
C#Entity Framework CoreJSON functions in SQL
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Look at how EF.Functions translations are implemented for other functions in the SQL Server and SQLite providers. Check files like src/EFCore.SqlServer/Query/Internal/SqlServerQueryableExtensions.cs and src/EFCore.Sqlite/Query/Internal/SqliteQueryableExtensions.cs. Also review existing tests for similar translations to understand the pattern. The issue requests adding translations for JSON VALUE/JSON QUERY for SQL Server and json extract for SQLite, so start by identifying the corresponding SQL function names and mapping them in the providers.
Provide EF.Functions translations for JSON functions · dotnet/efcore#29306 | Good First Issue