(w10: Is the second, upper case set of entries (SPANISH EYES) used for
case insensitive searches?)
We have a "title" and a "titlesearch" attribute in the database. The
latter would be a simplified version of the former. No special
characters, no dots etc. "Björk ft. Me" -> "BJORK FT ME". I put both in
the fulltext index to remain flexible.
(A search for the sample size only got the song, but not the album
containing it as a result. A search for the title gives both. Just
As you can see from the code I've referenced I'm only adding select
attributes of a track to the album index. Sample size obviously isn't
part of it.
But nobody would use the complete path in a search. So I tried that
also.
Code:
--------------------
/share/Multimedia/Music/FLACs/Modern/Madonna/
--------------------
As there are no spaces in this path, I'd expect it to trigger only when
matching the whole string.
I guess the tokenizer would split that string on the /. Resulting in
"Madonna" matching the first tracks's title. And as title is a w10 item
it appears top of the list.
--
Michael
_______________________________________________
plugins mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/plugins
