Tokenize and build FTS query string for postgres and sqlite #3933
Conversation
This file contains 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
alexshtin
approved these changes
Feb 10, 2023
rodrigozhou
force-pushed
the
sql-fts-tokenizer
branch
from
f06362b to
39e8447
Compare
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.
What changed?
Tokenize and build FTS query string for PostgreSQL and SQLite.
Why?
PostgreSQL and SQLite have a specific syntax for FTS query strings.
How did you test it?
Start server, and ran workflow trying different query strings. Checked the built query is correct.
Potential risks
No risks.
Is hotfix candidate?
No.