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.