Ensure PerformUpdate method should not be called within a read-only transaction
#9492
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
ReubenBond
approved these changes
May 12, 2025
scalalang2
changed the title
PerformUpdate method should not be called within a read-only trasnactionPerformUpdate method should not be called within a read-only transaction
ReubenBond
reviewed
May 12, 2025
Co-authored-by: Reuben Bond <[email protected]>
ReubenBond
approved these changes
May 12, 2025
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Background
The transactional method with
[ReadOnly]attribute states that It's a read-only transaction, which is not intended to allowPerformUpdatewithin the transactional context.Review
I'm not sure if this is the right approach.
Microsoft Reviewers: Open in CodeFlow