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

Eager load all navigation properties #4851

Closed
deenairn opened this issue Mar 18, 2016 · 2 comments
Closed

Eager load all navigation properties #4851

deenairn opened this issue Mar 18, 2016 · 2 comments
Labels
closed-no-further-action The issue is closed and no further action is planned. customer-reported

Comments

@deenairn
Copy link

Is there a mechanism to eager load all navigation properties (and any navigation properties they have) without having to do repeated calls to Include().IncludeThen(), etc. This is pretty labourious in our circumstances and error prone if new properties must be added then they must be added to this sequence of Include().IncludeThen().

Previously this worked via lazy loading - I know issue #3797 is there to resolve how to support this.

@rowanmiller
Copy link
Contributor

We probably don't want a "just Include everything" switch, since then you would quickly end up with the entire database loaded into memory. But we do have a couple of existing features that we want to implement that would help here. Rule based eager loading would require setup, but avoids having to explicitly include stuff all the time (#2953). We also want to support some for of defining aggregates, where it probably does make sense to allow automatically loading a complete aggregate when you are for one of the entities within it (#1985).

@baratgabor
Copy link

Where I ran into this need (or let's call it a desire) is actually integration testing. Specifically when I want to do asserts on the completeness of added or modified entities. Would be great to have assurance that everything related to the given entity is loaded automatically, and the amount of data or the performance in this use case is never gonna be a concern.

@ajcvickers ajcvickers added closed-no-further-action The issue is closed and no further action is planned. customer-reported labels Nov 16, 2021
@ajcvickers ajcvickers reopened this Oct 16, 2022
@ajcvickers ajcvickers closed this as not planned Won't fix, can't repro, duplicate, stale Oct 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-no-further-action The issue is closed and no further action is planned. customer-reported
Projects
None yet
Development

No branches or pull requests

4 participants