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 postsTPT: Use composition or TPH, or use viewsSpatial: Use SqlGeography and SqlGeometry or materialize to byte[], and FromSql, function mappingStored procedure mapping: ExecuteSqlCommand, triggers, updatable views, etc.- Graphical visualization of model: use third-party tools
Entity splitting: views- Change tracking proxies
Missing lifecycle hooksSimple logging: simple patterns to hook up loggingInterception: use diagnosticsFiltered 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
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 postsTPT: Use composition or TPH, or use viewsSpatial: Use SqlGeography and SqlGeometry or materialize to byte[], and FromSql, function mappingStored procedure mapping: ExecuteSqlCommand, triggers, updatable views, etc.Entity splitting: viewsMissing lifecycle hooksSimple logging: simple patterns to hook up loggingInterception: use diagnosticsFiltered Include: use conditions and short-circuiting in global filtersIt 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