fix(sqlite): configure busy_timeout on SQLite connections - #659
Merged
Conversation
- Configure PRAGMA busy_timeout = 5000 in SqliteConnection.connect() onOpen - Prevent immediate SQLITE_BUSY / database locked errors during concurrent disk access - Add unit test verifying PRAGMA busy_timeout on connection initialization Closes #656
Merged
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
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.
Description
Resolves #656 by configuring
PRAGMA busy_timeout = 5000;on SQLite connections:Lock Resilience:
PRAGMA busy_timeout = 5000;to theonOpencallback inSqliteConnection.connect().DatabaseException(database is locked / SQLITE_BUSY)failures when the SQLite file is concurrently accessed by background threads, file watchers, or other processes.Testing:
test/core/database/sqlite_connection_test.dartverifying thatPRAGMA busy_timeoutreturns 5000 on connection open.Closes #656