Skip to content

Expand SQLite comment to talk about busy_timeout#913

Merged
brandur merged 1 commit into
masterfrom
brandur-busy-timeout
May 24, 2025
Merged

Expand SQLite comment to talk about busy_timeout#913
brandur merged 1 commit into
masterfrom
brandur-busy-timeout

Conversation

@brandur

@brandur brandur commented May 22, 2025

Copy link
Copy Markdown
Contributor

Another small one. While writing documentation for SQLite tonight I
tried using busy_timeout as an alternative to setting a maximum of one
active connection. It kind of works, but I found overall that I'd still
get SQLITE_BUSY errors with busy_timeout once iterating the test
suite at higher counts like -count 100.

Overall, I think the single active connection is still the way to go.
Here, add a note on that so I won't forget about this in the future.

Another small one. While writing documentation for SQLite tonight I
tried using `busy_timeout` as an alternative to setting a maximum of one
active connection. It kind of works, but I found overall that I'd still
get `SQLITE_BUSY` errors with `busy_timeout` once iterating the test
suite at higher counts like `-count 100`.

Overall, I think the single active connection is still the way to go.
Here, add a note on that so I won't forget about this in the future.
@brandur brandur requested a review from bgentry May 22, 2025 05:52
@brandur brandur merged commit 057b587 into master May 24, 2025
10 checks passed
@brandur brandur deleted the brandur-busy-timeout branch May 24, 2025 00:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants