MediaMonkey forum

These searches give different results.

Search Bar:artist:Mel Torme(115 tracks)
Search Bar:artist:Mel Tormé(115 tracks)
Search->Artist:Mel Torme(17 tracks)
Search->Artist:Mel Tormé(115 tracks)

The 17 track case is not a subset of the 115 tracks. It includes 13 tracks for "Gerry Mulligan, Mel Torme, George Shearing" which are not included in the 115 plus 4 multi artist tracks.

Note: there is no diacritical in the additonal track artist tags.

Edit:
Search Bar:Mel Torme(130 tracks=115 + 13 + 2Composer contains Mel Torme)

Well, I know what is happening.
The other 4/17 contained "Mel Torme" and "Mel Tormé", eg. "Mel Tormé; Artie Shaw And His Orchestra featuring Mel Torme and His Mel-Tones".

There appears to be no way to construct a diacritical insensitive search of Artist/Album Artist, ie. tracks = 128.

Ummm. This is working now in 1281 for both Artist and Composer searches.
Nothing I can see in change log, but, ...

And, it's back with 1282.

Is anyone else seeing this?

It's a fairly important issue to me as I have a lot of artists/composers with diacriticals.

Well. More testing in 1282.
Search bar "artist:mel torme" works and returns expected 128 tracks via diacritical insensitive MATCH on SongsText.
Search dialog (Artist->mel torme) is diacritical sensitive via LIKE on Artists.

I must have just tested search bar in 1281.

Owyn,
we have always searched via Search dialog (Artist->mel torme) as diacritical sensitive via LIKE on Artists.
i.e. not using SQLite's FTS3.

But Search bar "artist:mel torme" is diacritical insensitive MATCH on SongsText (using FTS3)

As I now japanese users uses search dialog, because they can search also middle of the words ('donna' finds 'maddona')
and the others uses Search bar "artist:mel torme", because it is diacritical insensitive.

We should probably somehow unify this, but I think we should leave it for 4.0, once we resolve issue
http://www.ventismedia.com/mantis/view.php?id=5565

I added the note to the issue (this way it is tracked)

Ludek.

Ludek:
No problem, I understand exactly what is happening.

The original problem was raised when I got completely unexpected search results using 1280 (see first post).

The problem magically fixed itself with 1281.

@Ludek
Got another case which I think is involved with Search escaping characters.

How would I search for Genre starting with ";", ie. the equivalent of

Owyn,
you can search for ; via searchbar by typing ;

As you mean it doesn't work via search dialog -> Genre: ;
but I think it isn't a big deal, because ; is usually used as separator for multiple genres like Rock;Pop

> but I think it isn't a big deal, because ; is usually used as separator for multiple genres like Rock;Pop
Yeah. It is a pretty obscure use case. I was cleaning up after some RegExp appends of "; Cover" to Genre where Original Artist was known. In some cases Genre was blank before the append.

I had manually corrected several as I noticed them and wanted to see if I had missed any. The SELECT worked to find the one I missed and I can use it again if needed. Having it via Search would have allowed me to save the Search as an Auto-playlist. e.g. "Auto Fix ; at start of Genre".

No big deal, and Genres.GenreName LIKE ";%" would not find it anyway.

Not worth changing anything.