Commit History

Autor SHA1 Mensaxe Data
  dan 0cd2ffffb7 Fix the fts5 trigram tokenizer so that it handles non-nul-terminated strings. hai 1 mes
  dan 59b4f75e0f Add test case for fts5 trigram tokenizer. hai 1 mes
  dan ef2401f669 Tests to improve coverage of fts5_expr.c. hai 4 meses
  dan b651084713 Add tests to restore coverage of fts5_tokenizer.c. hai 4 meses
  dan 189c41221d Further tests and fixes for this branch. hai 4 meses
  drh e9b919d550 Improved robustness of parsing of tokenize= arguments in FTS5. hai 4 meses
  dan d548f74024 Fix a problem with the fts5 highlight() and snippet() functions when used with tokenizers like "trigram" that output overlapping tokens. Forum post [forum:/forumpost/63735293ec|63735293ec]. hai 1 ano
  dan a3e6192941 Fix a problem with the fts5 trigram tokenizer and LIKE or GLOB patterns for which contain runs of 2 or fewer non-wildcard characters that are 3 or more bytes when encoded as utf-8. hai 1 ano
  drh 8210233c7b Revise tests cases to align with the new EXPLAIN QUERY PLAN output. %!s(int64=3) %!d(string=hai) anos
  dan f46be6a1b9 Allow fts5 trigram tables created with detail=column or detail=none to optimize LIKE and GLOB queries. Allow case-insensitive tables to optimize GLOB as well as LIKE. %!s(int64=4) %!d(string=hai) anos
  dan 12a6a1eaf9 Fix a segfault caused by running "column LIKE NULL" against an fts5 table using the trigram tokenizer. Fix for [e33ee62575fc22]. %!s(int64=4) %!d(string=hai) anos
  dan 95dca8d0cf FTS5 does not handle tokens that contain embedded nul characters. Prevent the trigram tokenizer from returning such tokens. Fix for [2ba5930b2]. %!s(int64=4) %!d(string=hai) anos
  dan ccf578d435 Add tests for the trigram tokenizer. Fix minor issues. %!s(int64=4) %!d(string=hai) anos
  dan 33a99fad08 Add experimental unicode-aware trigram tokenizer to fts5. And support for LIKE and GLOB optimizations for fts5 tables that use said tokenizer. %!s(int64=4) %!d(string=hai) anos