Skip to content
Discussion options

You must be logged in to vote

XA transactions remain uncommitted by nature, so under the default isolation level, another database connection cannot read the uncommitted data.
If you need to perform a repeated read of the same data (for consistency), you must do so within the same local transaction, rather than splitting the operations across multiple separate local transactions.
This isn't a Seata-specific design—it's the standard behavior of XA transactions.

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by funky-eyes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants