We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently, this plugin only supports one connection per database, whereas sqlite does support multiple connections. Check out this article for info on that: http://charlesleifer.com/blog/sqlite-small-fast-reliable-choose-any-three-/
And because there is only one connection, contention can occur between simultaneous requests that can causes errors and even possible corruption.
The plugin should expose sqlite's support for concurrency by allowing for multiple connections, ideally even a way to manage a connection pool.
And in the meantime, perhaps the plugin should add a request queue to enforce that requests are processed one at a time, and prevent interference.
Some related issues are:
@brodybits
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Currently, this plugin only supports one connection per database, whereas sqlite does support multiple connections. Check out this article for info on that:
http://charlesleifer.com/blog/sqlite-small-fast-reliable-choose-any-three-/
And because there is only one connection, contention can occur between simultaneous requests that can causes errors and even possible corruption.
The plugin should expose sqlite's support for concurrency by allowing for multiple connections, ideally even a way to manage a connection pool.
And in the meantime, perhaps the plugin should add a request queue to enforce that requests are processed one at a time, and prevent interference.
Some related issues are:
@brodybits
The text was updated successfully, but these errors were encountered: