dotnet/EntityFramework.Docs

Create article with workarounds for SQL Server features that don't have first-class support

Open

#685 opened on Apr 18, 2018

View on GitHub
 (3 comments) (0 reactions) (0 assignees)PowerShell (1,625 stars) (1,961 forks)batch import
good first issue

Description

  • Spatial: Not needed anymore
  • JSON:
    • Value converter to parse/serialize JSON
    • JSON_VALUE, JSON_QUERY and JSON_MODIFY in FromSql or function mapping
  • Temporal tables:
    • AS OF, FROM TO, BETWEEN AND, CONTAINED IN, ALL in FromSql
    • Custom SQL in migrations
  • SQL Graph:
    • MATCH in FromSql
    • custom SQL in migrations
    • Can node and edge tables be treated as normal tables?
  • Always encrypted:
    • Value converters
    • Custom SQL in migrations
    • AsEnumerable() for explicit client eval (e.g. for comparisons, LIKE, etc.)
  • Full Text Search
    • Create indexes with Sql in migrations
    • Use FreeText (and soon Contains) functions
    • Write FREETEXTTABLE and CONTAINS table query in FromSql, until we get TVF support.

Contributor guide

Tech stack
csharpsql
Domain
documentation
Issue type
documentation
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.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Entity Framework Core knowledgeSQL Server basicsMarkdown
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
The issue outlines specific SQL Server features lacking first class support in EF Core (JSON, SQL Graph, Full Text Search, etc.). Research should focus on existing workarounds documented in other EF Core documentation or community resources. The final article should provide step by step guidance for each feature, referencing relevant EF Core API and migration techniques. Check linked discussions and any prior comments for additional context.