View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004591 | MMW v4 | Playlist / Search | public | 2008-04-20 13:50 | 2008-04-26 11:25 |
| Reporter | Ludek | Assigned To | |||
| Priority | immediate | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Product Version | 3.0 | ||||
| Fixed in Version | 3.0 | ||||
| Summary | 0004591: The ';' as OR logical operator is not available in Basic search for some fields (Artist, Genre, Composer) | ||||
| Description | As reported here: http://www.mediamonkey.com/forum/viewtopic.php?t=28498 The ';' as OR logical operator is not available in Basic search for some fields (Artist, Genre, Composer). It is fixed in build 1163 and added to automated regressions testing. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1163 | ||||
|
|
I think that this 'fix' is a regression in the sense that the Basic search functions previously didn't support _any_ of the functions that are supported in the search bar, but now it supports only some. e.g. 'space': ='And', however, this isn't supported in the Basic tab because it wouldn't make sense there ';' = 'Or', however, in the context of e.g. 'Genre', it should mean AND. In other words, if Genre = Audiobook;Children, then searching on the basic tab for Genre='Audiobook;Children' should mean Audiobook AND Children. The fact that we use ';' to mean OR in the main search bar and AND in the track properties is a design issue, but adding this 'fix' only magnifies the problem. What do you think? |
|
|
Re: I think that this 'fix' is a regression in the sense that the Basic search functions previously didn't support _any_ of the functions that are supported in the search bar, but now it supports only some. This is not true. Launch MM 2.5 and input "kid;morning" to the Title field of basic search and you will se that tracks including "kid" OR "morning" in its title are in the results. Re: The fact that we use ';' to mean OR in the main search bar and AND in the track properties is a design issue, but adding this 'fix' only magnifies the problem. I don't think this is a problem, in case of searching it means OR as it meant in MM 2.5 too. The fact that ';' is also used as separator in multiple fields is another issue, but I don't believe that this conflicts somehow. It can be workarounded via advanced search. I think that current implementation is correct. |
