Re: Strange behaviour searching with ['songs', ] via jsonrpc

> What it boils down to is that the FTS plugin does not operate unless
> there is whitespace in the search term.

There are some optimizations in place:

- single character only checks in main columns only (no real FTS)
- keyword(s) plus single character does respect that character, too
- single, popular terms (found in more than 500 records) would search in 
main columns only

"Main columns": FTS can define different weights for different values. 
Eg. for an artist the name would have the heighest weight. For tracks 
where he contributed to he'd be found in a column with lower weight. Now 
if "Chicane" was a contributor on >500 tracks, in comments, album names 
whetever, that would be considered a "popular term". In this case that 
search would only return results where he was in the name or track 
title, but not where he was listed as contributor.

If you enable debug logging for plugin.fulltext you'll get warnings in 
those cases where the FTS is optimized away.