Fossil SCM

Help text: update two fts4 references to fts5.

stephan 2025-02-06 10:58 trunk
Commit 17eb363cd487d3408b3c440e2ff13e90a5ac0b04c6c5dfec3490f353125d15bf
1 file changed +2 -2
+2 -2
--- src/search.c
+++ src/search.c
@@ -18,11 +18,11 @@
1818
** This file contains code to implement a search functions
1919
** against timeline comments, check-in content, wiki pages, tickets,
2020
** and/or forum posts.
2121
**
2222
** The search can be either a per-query "grep"-like search that scans
23
-** the entire corpus. Or it can use the FTS4 search engine of SQLite.
23
+** the entire corpus. Or it can use the FTS5 search engine of SQLite.
2424
** The choice is an administrator configuration option.
2525
**
2626
** The first option is referred to as "full-scan search". The second
2727
** option is called "indexed search".
2828
**
@@ -1038,11 +1038,11 @@
10381038
sqlite3_create_function(g.db, "rank", 1, SQLITE_UTF8|SQLITE_INNOCUOUS, 0,
10391039
search_rank_sqlfunc, 0, 0);
10401040
zPat = search_simplify_pattern(zPattern);
10411041
blob_init(&sql, 0, 0);
10421042
if( search_index_type(0)==4 ){
1043
- /* If this repo is still using the legacy FTS4 search index, then
1043
+ /* If this repo is still using the legacy FTS5 search index, then
10441044
** the snippet() function is slightly different */
10451045
zSnippetCall = "snippet(ftsidx,'<mark>','</mark>',' ... ',-1,35)";
10461046
}else{
10471047
/* This is the common case - Using newer FTS5 search index */
10481048
zSnippetCall = "snippet(ftsidx,-1,'<mark>','</mark>',' ... ',35)";
10491049
--- src/search.c
+++ src/search.c
@@ -18,11 +18,11 @@
18 ** This file contains code to implement a search functions
19 ** against timeline comments, check-in content, wiki pages, tickets,
20 ** and/or forum posts.
21 **
22 ** The search can be either a per-query "grep"-like search that scans
23 ** the entire corpus. Or it can use the FTS4 search engine of SQLite.
24 ** The choice is an administrator configuration option.
25 **
26 ** The first option is referred to as "full-scan search". The second
27 ** option is called "indexed search".
28 **
@@ -1038,11 +1038,11 @@
1038 sqlite3_create_function(g.db, "rank", 1, SQLITE_UTF8|SQLITE_INNOCUOUS, 0,
1039 search_rank_sqlfunc, 0, 0);
1040 zPat = search_simplify_pattern(zPattern);
1041 blob_init(&sql, 0, 0);
1042 if( search_index_type(0)==4 ){
1043 /* If this repo is still using the legacy FTS4 search index, then
1044 ** the snippet() function is slightly different */
1045 zSnippetCall = "snippet(ftsidx,'<mark>','</mark>',' ... ',-1,35)";
1046 }else{
1047 /* This is the common case - Using newer FTS5 search index */
1048 zSnippetCall = "snippet(ftsidx,-1,'<mark>','</mark>',' ... ',35)";
1049
--- src/search.c
+++ src/search.c
@@ -18,11 +18,11 @@
18 ** This file contains code to implement a search functions
19 ** against timeline comments, check-in content, wiki pages, tickets,
20 ** and/or forum posts.
21 **
22 ** The search can be either a per-query "grep"-like search that scans
23 ** the entire corpus. Or it can use the FTS5 search engine of SQLite.
24 ** The choice is an administrator configuration option.
25 **
26 ** The first option is referred to as "full-scan search". The second
27 ** option is called "indexed search".
28 **
@@ -1038,11 +1038,11 @@
1038 sqlite3_create_function(g.db, "rank", 1, SQLITE_UTF8|SQLITE_INNOCUOUS, 0,
1039 search_rank_sqlfunc, 0, 0);
1040 zPat = search_simplify_pattern(zPattern);
1041 blob_init(&sql, 0, 0);
1042 if( search_index_type(0)==4 ){
1043 /* If this repo is still using the legacy FTS5 search index, then
1044 ** the snippet() function is slightly different */
1045 zSnippetCall = "snippet(ftsidx,'<mark>','</mark>',' ... ',-1,35)";
1046 }else{
1047 /* This is the common case - Using newer FTS5 search index */
1048 zSnippetCall = "snippet(ftsidx,-1,'<mark>','</mark>',' ... ',35)";
1049

Keyboard Shortcuts

Open search /
Next entry (timeline) j
Previous entry (timeline) k
Open focused entry Enter
Show this help ?
Toggle theme Top nav button