Fossil SCM
Corrected a bit of misinformation in search.c's comments, per a report in the forum.
Commit
6d6880c8304dcf3993758d273158942315ddde7447b51dee2b7e4449876d5af3
Parent
e65544571e21c70…
1 file changed
+2
-2
+2
-2
| --- src/search.c | ||
| +++ src/search.c | ||
| @@ -18,12 +18,12 @@ | ||
| 18 | 18 | ** This file contains code to implement a search functions |
| 19 | 19 | ** against timeline comments, check-in content, wiki pages, tickets, |
| 20 | 20 | ** and/or forum posts. |
| 21 | 21 | ** |
| 22 | 22 | ** The search can be either a per-query "grep"-like search that scans |
| 23 | -** the entire corpus. Or it can use the FTS4 or FTS5 search engine of | |
| 24 | -** SQLite. The choice is a administrator configuration option. | |
| 23 | +** the entire corpus. Or it can use the FTS4 search engine of SQLite. | |
| 24 | +** The choice is a administrator configuration option. | |
| 25 | 25 | ** |
| 26 | 26 | ** The first option is referred to as "full-scan search". The second |
| 27 | 27 | ** option is called "indexed search". |
| 28 | 28 | ** |
| 29 | 29 | ** The code in this file is ordered approximately as follows: |
| 30 | 30 |
| --- src/search.c | |
| +++ src/search.c | |
| @@ -18,12 +18,12 @@ | |
| 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 or FTS5 search engine of |
| 24 | ** SQLite. The choice is a administrator configuration option. |
| 25 | ** |
| 26 | ** The first option is referred to as "full-scan search". The second |
| 27 | ** option is called "indexed search". |
| 28 | ** |
| 29 | ** The code in this file is ordered approximately as follows: |
| 30 |
| --- src/search.c | |
| +++ src/search.c | |
| @@ -18,12 +18,12 @@ | |
| 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 a administrator configuration option. |
| 25 | ** |
| 26 | ** The first option is referred to as "full-scan search". The second |
| 27 | ** option is called "indexed search". |
| 28 | ** |
| 29 | ** The code in this file is ordered approximately as follows: |
| 30 |