Efcore: Relational: Entity splitting support

[divega]

This work item represents the mapping capability to slice the data contained by an object into multiple tables.

Limitations:

• Properties mapped to multiple columns can't use store-generated values
• Foreign keys and indexes split across tables won't be created in the database

[ilmax]

I would love if this feature does not fill in the standard Relational library but perhaps is exposed as a additional feature (pay for play scenario) which I can plug in only if needed

[AndriySvyryd]

Related to TPT https://github.com/aspnet/EntityFrameworkCore/issues/2266

[ajcvickers]

Note: consider optional relationships: #9773

[AndriySvyryd]

The implementation could be simplified if we used a database model #8258

[netspark]

Would be very appreciated for implementing this, we have a lot of legacy one-to-one tables in DB which make no sense to treat separately in backend

[jansomers]

Would very much love this feature, also the optional relationships is a must have when implementing entity splitting

[maurei]

Any update? Would love to see this feature incorporated.

[ajcvickers]

@maurei This issue is in the Backlog milestone. This means that it is not going to happen for the 3.0 release. We will re-assess the backlog following the 3.0 release and consider this item at that time. However, keep in mind that there are many other high priority features with which it will be competing for resources.

[GeorgeTsaplin]

I suppose what Owned Entity Types can be used as an alternative for Entity Splitting and it's already implemented at EFCore 2.0.

[artyomtserashkovich]

Hi. Do you have any update?

[ajcvickers]

@ArtemTereshkovich This issue is in the Backlog milestone. This means that it is not going to happen for the 3.0 release. We will re-assess the backlog following the 3.0 release and consider this item at that time. However, keep in mind that there are many other high priority features with which it will be competing for resources.

[mister-conor]

This feature is a must for people migrating legacy systems to EF.

[leus]

Yes please - consider the scenario where a table is split for patitionin causes (for example, to separate LOB and row data).

[bairog]

Lacking this feature in EF Core stops me (like other people) from migrating legacy projects from EF 6.4.
@ajcvickers Do you have any concrete plan/schedule? What does "considered-for-net-release" label mean? .NET 5 (scheduled in November 2020) or .NET Core 3.x (may happend earlier)?

[AndriySvyryd]

@bairog We'll consider adding it to EF Core 5 if there's enough time left, otherwise it will likely go into EF Core 7

[bairog]

Hello. Do you have any updates? Is it going to be included to EF Core 5 release?

[roji]

@bairog no, this feature did not make it into the upcoming 5 release. We'll consider this again for the 6.0 planning