Query: FromSql with auto-included navigations sharing same table

[smitpatel]

This is not about owned entities which are eagerly loaded always and share table by convention.

This is specifically about user configuration when table is shared and also the navigation is marked as AutoInclude.

If user specify FromSql on an entity sharing table (principal/dependent either side is fine), and if the other side is getting included due to AutoInclude, is it good assumption to make that FromSql will also provide the data about the other side?

Currently since there is no ownership or weak entity, each entity type is separate query root and they use their own mapping so the other side will generate a join and get data from the table where it is stored.

[smitpatel]

Also @AndriySvyryd wrote

@smitpatel I understand that it's possible, it just seems ambiguous as to what shape FromSql expects when there are auto-includes with table-splitting. Perhaps this (and the owned case) can be overridden by an explicit Include.

[smitpatel]

Also see #14525 which is about FromSql for whole query (query root + all includes)

[ajcvickers]

Notes from triage:

• We need to consider this from a holistic perspective--see Define consistent behaviors for FromSql and ToQuery methods used with complex mappings #21888
• For 5.0, we will special case owned types that are auto-included to avoid a break now from 3.1.

[smitpatel]

Blocked on #21888