View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0015142 | MMW 5 | Playlists (Auto) / Search / Filters | public | 2018-10-11 23:39 | 2022-09-14 14:39 |
| Reporter | peke | Assigned To | |||
| Priority | high | Severity | tweak | Reproducibility | always |
| Status | assigned | Resolution | open | ||
| Product Version | 5.0 | ||||
| Target Version | 5.2 | ||||
| Summary | 0015142: Search: Multi valued fields | ||||
| Description | Some fields do not comply with multi value search where others do. FAIL: genre: contains - pop;wave;pop-rock genre: does not contain - soft;hard WORKS: genre: contains - pop;wave;pop-rock genre: does not contain - soft genre: does not contain - hard | ||||
| Additional Information | https://www.mediamonkey.com/forum/viewtopic.php?f=1&t=91350 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
Yes, "doesn't contain" operator has always excluded a whole string contained within the text field To exclude multiple values users can use 'doesn't equal' operator So yes, to exclude multiple sub-strings users need to use: genre: does not contain - 'string1' genre: does not contain - 'string2' rather than genre: does not contain - 'string1;string2' |
|
|
Moved for Tweaking in MM5 and assigned to Jiri to triage the best approach due the changes in Advanced search UI we made in MM5. It was strange (unexpected) that just changing Drop down from 'Contain' to 'Do not contain' behave differently. |
|
|
Not too important imho, but yes, I'd say that {genre: does not contain - 'string1;string2'} should exclude all tracks with at least one of the genres. |
