-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Owned entities + lazy loading #2382
Labels
Comments
See dotnet/efcore#10787 and dotnet/efcore#12462 In particular, dotnet/efcore#12462 is fixed in the EF Core 5 previews which are available now on NuGet and should stop owned properties from being lazy-loaded. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Why after using loading for context i'm forced to use it for each and every entity/navigation property?
By turning on lazy loading for context, all my navigation properties needs to be lazy ones. When I combine it with entity having owned type it causes having additional join in SQL read (from the same table to the same one). Finally having one row with 4 owned types (4 of the same type, each having two columns), instead of having single "select columns from table",
I have such overheaded SQL:
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: