View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0003394 | MMW v4 | Playlist / Search | public | 2007-08-15 19:49 | 2007-08-19 16:06 |
Reporter | rusty | Assigned To | |||
Priority | urgent | Severity | feature | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Product Version | 3.0 | ||||
Fixed in Version | 3.0 | ||||
Summary | 0003394: Multiple Definition Fields: searching algorithm is unclear | ||||
Description | When 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'. | ||||
Tags | No tags attached. | ||||
Fixed in build | 1061 | ||||
|
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. |
|
Verified 1061. |