Prune main table in entity splitting if not used

[smitpatel]

Considerations

• Optional dependents Optional dependents and entity splitting #29079 we currently check main table for figuring out property condition for materialization, if we drop main fragment we need to see how to generate that condition.
• Optional fragments, when additional tables won't have row so we would need to join with main fragment to make sure we identify null data vs no data. Entity Splitting: allow optional split table #27974

From implementation perspective,
Multiple columns coming from different fragment mapped to same IProperty will have same value. Currently we pick the first column in that list (which is like to be coming from main table which we don't remove yet). In order to prune in best way, we would need to understand at the time of pruning what are the column values we need and how to generate those columns by utilizing least number of tables participating in the entity splitting. #29035 may be necessary for it.

[n0099]

Is there any plan for implementing this feature?

[ajcvickers]

This issue is in the Backlog milestone. This means that it is not planned for the next release (EF Core 8.0). We will re-assess the backlog following the this 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. Make sure to vote (👍) for this issue if it is important to you.