13
Provide true fuzzy match options in Supabase JS Text Search
Source: supabase/supabase#19453 · opened by @plasmatech8
Currently, the textSearch functionality within Supabase JS is limited to options like "plain", "phrase", and "websearch". However, it lacks support for typo-correction or genuine fuzzy matching capabilities. The current implementation of .textSearch() and the underlying tsvector functionality relies on lexemes. However, it is worth noting that this approach (as described in the [docs]( is presented as "fuzzy matching”, but might not entirely align with the conventional understanding of fuzziness. Encountering limitations when dealing with mispelled non-standard English words or those without a corresponding lexeme can be a bit frustrating for users - depending on the domain of the application. I am wondering if there are any plans to introduce some form of fuzzy matching feature within the JavaScript client. This may potentially need to utilise extensions such as pg_bm25, fuzzystrmatch, pg_trgm, or work by making adjustments to the to_tsvect…
No pledges yet. Be the first to back this.
Comments
Similar requests
Suggestion: Renaming some filters
1 vote · 0 comments
Custom headers not being sent along with the requests in createPagesServerClient (NextJS)
2 votes · 0 comments
AuthException(message: AuthRetryableFetchError, statusCode: null)
4 votes · 0 comments
Edge Functions: Allow package.json without import_map.json
6 votes · 0 comments
Proper editor for JSON(B) fields
2 votes · 0 comments
No comments yet.