Skip to content
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

Improve description of single/split queries #4201

Merged
merged 1 commit into from
Jan 10, 2023
Merged

Conversation

roji
Copy link
Member

@roji roji commented Jan 9, 2023

Introduce the distinction between cartesian explosion and the (less important) data duplication, and provide examples.

See dotnet/efcore#29665 for a discussion around this.

Introduce the distinction between cartesian explosion and the (less
important) data duplication, and provide examples.
@roji roji merged commit 5395234 into dotnet:main Jan 10, 2023
@roji roji deleted the Cartesian branch January 10, 2023 20:52
roji added a commit to roji/EntityFramework.Docs that referenced this pull request Jan 10, 2023
roji added a commit to roji/EntityFramework.Docs that referenced this pull request Jan 10, 2023
roji added a commit to roji/EntityFramework.Docs that referenced this pull request Jan 10, 2023
roji added a commit that referenced this pull request Jan 10, 2023
@KesavaSubhash
Copy link

Hy this is Subhash ...
I need to work with Data Loading of lazy, Eager and explicit .. Basically im confusing to prepare navigation properties in entity level ,
Here I have an Module like Pricelist with Four Foreign Keys how i can Prepare Navigation Properties .. , Here we consider Table names (Foreign keys tables) as A ,B,C ,D Main table is PriceList

@roji
Copy link
Member Author

roji commented Sep 19, 2023

@KesavaSubhash the documentation on the different types of loading (eager, explicit, lazy) is here. You should generally default to using eager loading with Include (in single or split query mode) unless you have some specific requirements; for example, you can use explicit loading if you don't know which dependents you need at the point where you load your principal (this is generally rare). Lazy loading should generally be avoided.

If you have further questions, please open a new issue with a description of what you're trying to achieve and specific questions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants