[release/7.0] Support entities with owned types in ExecuteUpdate setter property lambda #29723
Conversation
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
…ter property lambda (dotnet#29672) Fixes dotnet#29618 Fixes dotnet#28727 (cherry picked from commit d4be66b)
AndriySvyryd
approved these changes
Dec 1, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Fixes #28727, backports #29672
Description
The logic for verifying and handling property selectors for ExecuteUpdate does not take into account owned entities.
Customer impact
ExecuteUpdate does not work when the entity being updated has an owned entity (even if the update doesn't affect that owned entity).
How found
Customer reported on 7.0
Regression
No.
Testing
Added a test for the affected scenario.
Risk
Low; the fix is quite trivial, and a quirk was added to revert back to older behavior.