dotnet/EntityFramework.Docs

Create article with workarounds for missing popular features

Open

#684 建立於 2018年4月17日

在 GitHub 查看
 (1 留言) (1 反應) (0 負責人)PowerShell (1,625 star) (1,961 fork)batch import
area-port-from-ef6good first issue

描述

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, 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 Related: #1971, #3919

貢獻者指南

技術棧
csharp
領域
documentation
議題類型
documentation
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
familiarity with Entity Framework Core and EF6basic Markdownunderstanding of documentation contribution guidelines
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
80
研究方向
Look at the existing documentation in the porting section (https://docs.microsoft.com/en us/ef/efcore and ef6/porting/). Add workarounds for graphical visualization of model (use third party tools) and change tracking proxies. See related issues #1971, #3919. Consider referencing the gist and blog post linked in the issue.