Throw when attempting to lazy-load after no-tracking query #10851
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
anpete
approved these changes
Feb 2, 2018
Part of #10042, #10509, #3797 It would be good to make this work in a future release, but this involves running a no-tracking query with fixup where the root entity is already materialized. For now, this will throw so we can make it work later without it being a breaking change. Lazy-loading behaviors for non-tracked entities: * Proxies: * No-op if entity was explicitly detached * Throw if it was queried as no-tracking * Lazy-loading entities with loader service property: * No-op if entity was explicitly detached * Throw if it was queried as no-tracking * Lazy-loading entities without service property: * Throw even if entity was explicitly detached, but entity can set loader to null, or a service property can be defined * Throw if it was queried as no-tracking
ajcvickers
force-pushed
the
TinyTearsMakeUpTheOcean0201
branch
from
951e6b2
to
4df8e7b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Part of #10042, #10509, #3797
It would be good to make this work in a future release, but this involves running a no-tracking query with fixup where the root entity is already materialized. For now, this will throw so we can make it work later without it being a breaking change.
Lazy-loading behaviors for non-tracked entities: