-
Hello! song_fulltext_search(:match_string AS TEXT):
SELECT
CAST(BM25(songs_fts, 0.0, 0.0, 10.0, 0.5, 5.0, 5.0, 2.0, 0.0) AS REAL) AS rank
,uuid
,source_bank_id
,pitch_field
,CAST(SNIPPET(songs_fts, 2, '<?', '?>', '...', 30) AS TEXT) AS match_title
,CAST(SNIPPET(songs_fts, 3, '<?', '?>', '...', 30) AS TEXT) AS match_lyrics
,CAST(SNIPPET(songs_fts, 4, '<?', '?>', '...', 30) AS TEXT) AS match_composer
,CAST(SNIPPET(songs_fts, 5, '<?', '?>', '...', 30) AS TEXT) AS match_poet
,CAST(SNIPPET(songs_fts, 6, '<?', '?>', '...', 30) AS TEXT) AS match_translator
FROM songs_fts
WHERE songs_fts MATCH :match_string
ORDER BY rank; With FTS5, BM25 can be used to assign weights to each column for ranking. A query like above runs fine with SQLite.
Am I doing something wrong, or should I just disable this warning? |
Beta Was this translation helpful? Give feedback.
Answered by
simolus3
Oct 17, 2024
Replies: 1 comment 3 replies
-
Drift is doing something wrong here, I was not aware of the option to assign weights. You can ignore the warning for now, I don't think we have a way to explicitly ignore warnings at the moment. Edit: Fixed in f692bb1. |
Beta Was this translation helpful? Give feedback.
3 replies
Answer selected by
RedyAu
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Drift is doing something wrong here, I was not aware of the option to assign weights. You can ignore the warning for now, I don't think we have a way to explicitly ignore warnings at the moment.
Edit: Fixed in f692bb1.