When using SEARCH you need to type the word exactly as it appears in the
timeline.
I’m guessing it uses SQL’s LIKE to find the related matches.
So, if you’re looking for the word ‘scroll’ it won’t match ‘scrolling’ and vice
versa.
One suggestion is to append ‘%’ to the search term to match any ending variant
of the word. It’s usually the ending of a word that differs.
It could also use % on either side to find the sought term inside any bigger
word (perhaps with an option), perhaps ordering the exact matches before the
rest.
A 2nd related suggestion (this only with the use of an option) is to use the
SOUNDEX function to also catch sometimes misspelled words.
Thanks.
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
