Ensure all failed transactions are rolled back. #118
Merged
+148
−12
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.
Related to #46410
I only found one instance.
Basically any function that receives a transaction handle and returns a
non-nil error is responsible for ensuing the transaction is rolled back.
This is covered by any failed calls to
tx.Exec
ortx.StmtExec
butin this case
ListOptionIndexer#afterUpsert
can fail on other situations,and is therefore responsible for rolling back the transaction.