View Issue Details

IDProjectCategoryView StatusLast Update
0003394MMW v4Playlist / Searchpublic2007-08-19 16:06
Reporterrusty Assigned To 
PriorityurgentSeverityfeatureReproducibilityalways
Status closedResolutionfixed 
Product Version3.0 
Fixed in Version3.0 
Summary0003394: Multiple Definition Fields: searching algorithm is unclear
DescriptionWhen I search for Genre=Children
--> MM returns tracks, as would be expected, where:
Genre=Children
Genre=Accoustic;Children

When I search for Genre|=Children
--> MM returns tracks where:
Genre=Accoustic;Children
Genre=Children;Audiobook

i.e. it searches for anything that isn't an exact match of 'Children'.

I'm not sure if this is a bug, or if this is working as designed (and what the design might be), but it seems to me that a search for Genre|=Children:
-should certainly not return tracks where Genre=Children;Audiobook (if we assume that it's evaluating only on the first Genre)
-should possibly not return tracks where Genre=Children;Audiobook (if we assume it's evaluating on all Genres). BUT, if we agree on this, then we need to have a means of excluding Genre=Children or Genre=Children;x, possible by adding criteria such as 'Equals exclusively' 'doesn't equal exclusively'.
TagsNo tags attached.
Fixed in build1061

Relationships

related to 0000683 closedrusty Support for multiple-definition fields (genres) 

Activities

jiri

2007-08-15 22:52

administrator   ~0010144

Assigning to Ludek to fix the search problem, != should match tracks that don't have _any_ of its values (e.g. genres) equal to the one specified. (I wonder whethere EXCEPT SQL command can't be used successfully here in order to make the query fast - we can discuss over IM).

As for an operator for the exact match, I wouldn't care about it for now, can be considered for MM 3.1.

rusty

2007-08-19 16:06

administrator   ~0010194

Verified 1061.