Roll back failed transaction commits - #27
Merged
simolus3 merged 1 commit intoSep 10, 2026
Merged
Conversation
julianallchin
marked this pull request as ready for review
September 10, 2026 00:54
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.
What changed
COMMITsucceedsRoot cause
A deferred constraint can fail at commit and leave SQLite inside the transaction. The guard previously disabled rollback before attempting the commit, so later writes failed with
Connection already in transaction.This isolates the failed-commit fix included in #22 without adding public APIs.
Validation
cargo +1.97.1 test -p powersynccargo +1.97.1 clippy -p powersync --all-targets -- -D warningsThe regression fails before the fix and passes afterward.