Unexpected behavior using Table Splitting

[draudrau]

Hi all,

I am using table splitting to model composition association between two entities.
You can look at the project in attachment.

First I create the parent entity (Blog) without explicitely defining the child entity (Author).
Then I try to get the Blog entity with loading the child (Author). I am expecting the Author entity is loading (with all its properties to null).
But I get an exception. Author is null.
I think it's not relevant. Table splitting is appropriate to model composition association between two entities. In a composition, the Blog entity can't exist without the Author entity.
When I get the Blog entity with the Author entity, the Author should never be null.

TableSplittingIssue.zip

Further technical details

EF Core version: 3.1.1
Database provider: (e.g. Microsoft.EntityFrameworkCore.SQLite)
Target framework: (e.g. .NET Core 3.1.1)
Operating system: Windows 10 Pro 1909
IDE: (e.g. Visual Studio 2019 16.3)

[ajcvickers]

Duplicate of #12100.

@draudrau Not a great workaround, I know, but if one or more properties on the child are required, then you should get the behavior you want.

[draudrau]

Thanks for the workaround, I am doing like that for now.
It's just a bit frustrating when I dont need required property.

Good job, EF Core is a great ORM, very pleasant to use.