CAY-2902 Shared query cache clobbers newer object state#632
Merged
stariy95 merged 3 commits intoNov 6, 2025
Merged
Conversation
…ementation and added additional tests)
Contributor
Author
|
This behavior is fixed now. I did have to modify an existing test in DataContextPrefetchIT however, so give special attention to that change. |
johnthuss
changed the title
Member
|
Merged in master, will check everything once more before backporting this (or not) to 4.2 |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
When an object is returned from the Shared Query Cache it will overwrite the state of objects that had updates saved after the cache was populated, and return them to the previous state they were in when the cached query was run. There is a failing unit test demonstrating the problem.