View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009195 | MMW v4 | Playlist / Search | public | 2012-03-01 16:42 | 2012-05-01 14:48 |
| Reporter | lowlander | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 4.0.3 | ||||
| Target Version | 4.0.5 | Fixed in Version | 4.0.5 | ||
| Summary | 0009195: Search including OR throws SQL error in Quick Search | ||||
| Description | If you type a search of Artist1 OR Artist2 in the Quick Search an SQL error is thrown as instant results are loaded (Artist1 OR is an incorrect SQL query). | ||||
| Steps To Reproduce | Testing note: this may also occur with other SQL operators | ||||
| Additional Information | http://www.mediamonkey.com/forum/viewtopic.php?f=7&t=64833 Related: http://www.mediamonkey.com/forum/viewtopic.php?f=7&t=64889 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1484 | ||||
|
|
Fixed in build 1600 and merged into 4.0.4.1480 |
|
|
I can reproduce this in 1483 with quicksearch: artist:beatles OR artist: |
|
|
Fixed in build 1484. |
|
|
Verified 1484. |
|
|
I wonder if it would be more elegant that instead of not searching when user enters Artist1 OR (even on hitting Enter) that instead it should search, but ignore OR (and other database Operators) until they constitute a valid SQL statement (artist1 OR artist2). This means Artist1 OR would actually search for Artist1. |
|
|
Yes, it is probably reasonable, but it is a very minor issue and thus I am rather avoiding fixing this in order to prevent from introducing a regression. |
