don't rewrite the query root when attempting to track the results #132
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.
closes #129
The issue is that you can't query entities and have them be tracked, so this fails:
This is because
db.Entities.First()is rewritten intodb.Entities.Select(e => new Entity { ...e }).First()and this breaks entity tracking.So I introduced some fixes so that if tracking was going to happen then it wouldn't be rewritten. This is determined via the default tracking behavior, configured like:
or based on if
AsTrackingor AsNoTracking` is part of the query, eg:default applies first and can be overridden by using
AsTrackingorAsNoTrackingexplicitly. So if you want root rewriting by default, then I suggest you set the default tracking behavior toNoTrackingand everything will keep working as it does in the current release. If however you use tracking by default, then you can callAsNoTrackingorExpandProjectablesto rewrite the root query.