Tracked by Issue #3170: TPC inheritance mapping pattern For example, a hook for manipulation of entity instances after they are created, commonly known as ObjectMaterialized.
For EF7, we plan to add important missing hooks.
We have implemented many lifecycle hooks over the previous versions of EF Core, including various interceptors and events. Lifecycle hooks enable notification of an application or library whenever certain interesting conditions or actions occur for entities, properties, relationships, queries, context instances, and other EF constructs. Value proposition: Allow applications to react when interesting things happen in EF code. EF Core already combines changes to many tracked entities into batches when sending updates to the database via SaveChanges. Note that bulk updates is not the same as batching updates. This can be significantly faster than tracked updates, especially when the same modification must be applied to many different entities/rows.įor EF7, we plan to implement bulk updates and deletes (but not inserts). In contrast, bulk, or set-based, updates involve defining the changes that should be made to the database and then executing those changes without first loading entities into memory. However, it requires a database roundtrip to load entities into memory in order to create the appropriate database commands, followed by a database roundtrip to execute these commands. This mechanism ensures that database operations are ordered to satisfy constraints, and that tracked entities are kept in sync with the changes made to the database. Value proposition: Efficient, predicate-based updates for many database rows without loading data into memory.Ĭhange tracking followed by SaveChanges is the primary mechanism in EF Core for inserting, updating, and deleting entities. set-based) CUD operations (without loading data into memory) We will work with the community to align existing implementations for Npgsql and Pomelo MySQL, and also add support for SQL Server and SQLite. This feature will introduce a common mechanism and patterns for JSON support that can be implemented by any database provider. Value proposition: Save and query into JSON-based documents stored in relational database columns. Tracked by Issue #4021: Map JSON values stored in database to EF properties Based on these votes in addition to other factors, we plan to work on the following highly requested features for EF7. Theme: Highly requested featuresĪs always, a major input into the planning process comes from votes (👍) for features on GitHub. Please comment on GitHub Issue #26994 with any feedback or suggestions. The high-level status of each theme can be tracked in the EF Core biweekly updates. The large investments in EF7 will fall mainly under the following themes:Įach of these themes is described in detail below. Our goal is to minimize breaking changes as much as possible. Breaking changesĮF7 will contain a small number of breaking changes as we continue to evolve both EF Core and the. NET support policy and will therefore not be a long-term support (LTS) release. NET Standard version for more information see the future of. Supported platformsĮF7 currently targets. There are no plans for an EF Core 6.1 release. General informationĮF Core 7.0 is the next release after EF Core 6.0 and is currently scheduled for release in November 2022 at the same time as. Some things currently planned for EF7 may get punted out. Some things not currently planned for EF7 may get pulled in. This plan is not a commitment it will evolve as we continue to learn throughout the release.
0 kommentar(er)
