Build for use within a SQLite3 loadable extension#320
Open
mlin wants to merge 4 commits intoSRombauts:masterfrom
Open
Build for use within a SQLite3 loadable extension#320mlin wants to merge 4 commits intoSRombauts:masterfrom
mlin wants to merge 4 commits intoSRombauts:masterfrom
Conversation
8f42f71 to
49a568f
Compare
78946be to
6d089fc
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Greetings @SRombauts or maintainer whom it may concern
I have an interesting use case in which I want to use SQLiteCpp's convenient API within the implementation of a SQLite3 loadable extension. There are three bits needed,
SQLite::Databaseobject to wrap a givensqlite3*connection (passed to us as the extension is loaded) instead of opening a new one. Straightforward, but check my work?sqlite3ext.hinstead ofsqlite3.h, with reference to an extern symbol needed to make that work (usually hidden behind theSQLITE_EXTENSION_INIT1macro). Here activated by the newSQLITECPP_IN_EXTENSIONCMake option.SQLITECPP_IN_EXTENSIONWith the enclosed example, it all seems to work nicely. Thanks for consideration!