dotnet / dotnet/EntityFramework.Docs

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

Open
#685 3 comments 0 reactions 0 assignees View on GitHub
good first issue
Dominant language
Mermaid
Stars
1.7k
Forks
2k
Avg merge
7d 23h
Merged PRs (30d)
16

Description

- [ ] ~~Spatial:~~ Not needed anymore
- [ ] ~~Link to workarounds for [missing EF6 features article](https://github.com/aspnet/EntityFramework.Docs/issues/684)~~
- [ ] 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?
- [x] Always encrypted:
- [x] 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

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.