Repository navigation
Allow configuring the SQLite busy timeout with SQLITE_BUSY_TIMEOUT
#558
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
JanJakes
merged 5 commits into
WordPress:trunk
from
chubes4:fix/issue-548-sqlite-busy-timeout
Oct 28, 2026
+168
−17
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
e25ba0c
Allow configuring the SQLite busy timeout with SQLITE_BUSY_TIMEOUT
chubes4 4d66fa2
Remove the busy timeout docs from the plugin readmes
JanJakes 0e21f38
Rename the busy timeout option and use milliseconds
JanJakes f73719a
Validate the SQLite busy timeout
JanJakes c4d8490
Improve the busy timeout concurrency tests
JanJakes File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Script executed:
Repository: WordPress/sqlite-database-integration
Length of output: 6403
Script executed:
Repository: WordPress/sqlite-database-integration
Length of output: 444
Script executed:
Repository: WordPress/sqlite-database-integration
Length of output: 10365
Web query:
PHP PDO SQLite PDO::ATTR_TIMEOUT sqlite3_busy_timeout documentationResult:
Define precedence for the two busy-timeout options.
A caller can supply both options.
PDO::ATTR_TIMEOUTis applied afterPRAGMA busy_timeout, so it can replace the configuredsqlite_busy_timeout, including disabling the wait when set to0. The driver API documents neither option as the winner. Define the precedence and apply the winning value last. This is a narrow conflict for callers that set both options.