Add sqlite_busytimeout parameter as user configurable param #121
+79
−27
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.
Add sqlite busy_timeout parameter as user configurable param, this allows for more flexibility when having multiple writes into the single sqlite instance, as sqlite has file level locking that only permits one write at a time. The
busy_timeout
configuration allows for the writes that are waiting to obtain lock to wait for the duration specified bybusy_timeout
before reporting errorRuSqlite: Database is locked