dotnet / dotnet/EntityFramework.Docs
Create article with workarounds for missing popular features
- Dominant language
- Mermaid
- Stars
- 1.7k
- Forks
- 2k
- Avg merge
- 7d 23h
- Merged PRs (30d)
- 16
Description
This is an opportunity for us to provide some guidance on how to deal with the absence of some features until we have them. For example:
- ~Many-to-many: @ajcvickers' blog posts~
- ~TPT: Use composition or TPH, or use views~
- ~Spatial: Use SqlGeography and SqlGeometry or materialize to byte[], and FromSql, function mapping~
- ~Stored procedure mapping: ExecuteSqlCommand, triggers, updatable views, etc.~
- Graphical visualization of model: use third-party tools
- ~Entity splitting: views~
- Change tracking proxies
- ~Missing lifecycle hooks~
- ~Simple logging: simple patterns to hook up logging~
- ~Interception: use diagnostics~
- ~Filtered Include: use conditions and short-circuiting in global filters~
It should probably be part of the [porting section](https://docs.microsoft.com/en-us/ef/efcore-and-ef6/porting/), although workaround can be used in new applications as well.
Note that this is also not necesesarily for EF6 gaps (e.g. filtered include wasn't there).
Also see https://gist.github.com/JeffLeBertEpicor/3a044b5eb0277752d45b6186e3bb2549, [mikee.se/posts/migrating_from_ef6_to_ef_core](https://www.mikee.se/posts/migrating_from_ef6_to_ef_core)
Related: #1971, #3919
Contributor guide
Assessment
This issue has not been assessed yet.