Skip to content

max_connections(1) to avoid using multiple writers w sqlite. #305

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
merged 1 commit into from
Oct 28, 2021

Conversation

yaymukund
Copy link
Contributor

Closes #223

It is not supported. See: https://sqlite.org/wal.html#concurrency

"However, since there is only one WAL file, there can only be one writer
at a time."

It is not supported. See: https://sqlite.org/wal.html#concurrency

"However, since there is only one WAL file, there can only be one writer
at a time."
@yaymukund yaymukund force-pushed the sqlite-single-writer branch from a700a7d to 7e365b1 Compare October 27, 2021 21:29
Copy link
Contributor

@marsella marsella left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great, thanks for the thorough investigation.

@yaymukund yaymukund merged commit 13a5bcc into main Oct 28, 2021
@yaymukund yaymukund deleted the sqlite-single-writer branch October 28, 2021 16:18
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.

Redesign database tests to avoid locks
2 participants