dotnet/EntityFramework.Docs

Create article with workarounds for missing popular features

Open

#684 opened on Apr 17, 2018

View on GitHub
 (1 comment) (1 reaction) (0 assignees)PowerShell (1,625 stars) (1,961 forks)batch import
area-port-from-ef6good first issue

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, 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

Contributor guide

Tech stack
csharp
Domain
documentation
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
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
familiarity with Entity Framework Core and EF6basic Markdownunderstanding of documentation contribution guidelines
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80
Research direction
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.