My 0.02$ make the searc(hes) smarter , it does not cope well with
misspelled terms etc ?
So, some kind of "fuzzy" search? Based on what though? Not sure how well
something like soundex () works in practice. You would probably want to
build a table of soundex () values at scan time to check against since
it probably be a hefty query to run ad hoc each time. I know there are
some other techniques for finding near matches but I don't know which
are available in SQLite.
I haven't looked into this problem in detail yet. But yes, it sounds
simpler than it is. In particular as most of these simpler functions
always work on the full string (eg. the full track title), but you'd
like to get hits as quickly as possible, typing as little as possible.
In this case you can't just compare func(input) like func(output).
But it sounds like an interesting problem :-). I'll look into this when
I find time. But there are a few busy (and lazy ;-)) weeks ahead. Please
feel free to file an enhancement request (or update an existing one) on
bugs.slimdevices.com. Make sure I'm CCed on that bug report.
--
Michael
_______________________________________________
beta mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/beta
