-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Set default busy timeout to 5 seconds #929
Conversation
similar to: jgallagher/rusqlite@05b03ae this should reduce SQLITE_BUSY situation
Thanks. Can you provide a bit more information what this "SQLITE_BUSY situation" is and how this solves it? :)
… Am 02.06.2017 um 11:08 schrieb wangcong ***@***.***>:
similar to:
***@***.***
this should reduce SQLITE_BUSY situation
You can view, comment on, or merge this pull request online at:
#929
Commit Summary
• Set default busy timeout to 5 seconds
File Changes
• M diesel/Cargo.toml (1)
• M diesel/src/lib.rs (2)
• M diesel/src/sqlite/connection/raw.rs (16)
Patch Links:
• https://github.com/diesel-rs/diesel/pull/929.patch
• https://github.com/diesel-rs/diesel/pull/929.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
yeah, this deals with multiple concurrent sqlite writers. there are some discussions like here:and also these documentations:tldr:
reference: https://github.com/jgallagher/rusqlite/blob/master/src/row.rs#L43 |
I'd rather not introduce the log crate or warnings for this. We need to properly return an error here. |
this commit only logs the error, but can more refine grained method should be used. reference: https://github.com/jgallagher/rusqlite/blob/master/src/row.rs#L43
Updated :) |
@sgrif @killercup These changes turn out working well in our project, any ideas? |
We cannot accept a PR that simply has |
Going to close this, as it's been sitting around for a while. Feel free to re-submit if you're still interested in working on this. However for this to be accepted we'd need to present this error case to the user. Silently treating it as an empty result set is not an acceptable solution. |
similar to:
jgallagher/rusqlite@05b03ae
this should reduce SQLITE_BUSY situation