Use explicit write transactions during sync - #90
Open
antweb wants to merge 6 commits into
Open
Conversation
robbi5
approved these changes
Aug 13, 2026
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.
SQLDelight starts all transactions in the default DEFERRED mode. As a result, transactions that start with a read-only query but perform a write further down the line start off as a read-only transaction and are then upgraded to read-write on the fly.
If someone else holds a write lock at the moment of this upgrade, the transaction will instantly fail with an SQLITE_BUSY error - unlike explicit read-write transactions which would wait for a busy timeout first (if configured).
The easiest way to avoid this would be to start the transaction with BEGIN IMMEDIATE, but the SQLDelight APIs do not seem to provide this option. Until we find a better solution, issue a no-op write statement before the original transaction contents as a workaround. This will force an upgrade to a read-write transaction right away.