Compile sqlite with FTS3 enhanced query syntax enabled #562
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
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.
Fixes #550
This adds three compilation flags to the embedded sqlite module:
-DSQLITE_ENABLE_FTS3to explicitly enable FTS3 support (which AFAIK is already enabled by default)-DSQLITE_ENABLE_FTS3_PARENTHESISto enable the enhanced FTS3 query syntax (which isn't enabled by default)-DSQLITE_ENABLE_FTS3_TOKENIZERto enable the two-argument version of thefts3_tokenizer()interface. It still has to be enabled on the connection-level usingConnection.setconfigAll those flags are enabled by default in the Debian build of SQLite, and probably in other distributions as well.