Add a new RegisterBusyHandler method to SQLiteConn to allow access to sqlite3_busy_handler()
#1278
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
polyscone
force-pushed
the
feature/busy-handler
branch
from
e22c98c to
d20eddd
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR just adds a new
RegisterBusyHandlermethod to theSQLiteConntype to allow use of thesqlite3_busy_handler()function.I tried to follow the same style as the other
Register*methods which use thevoid*user data args as a way to pass a handle to a Go callback function to a trampoline function defined in C.I've also updated the
_examplesfolder with a new example file.Fixes #290