View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0017395 | MMW 5 | Playlists (Auto) / Search / Filters | public | 2021-01-16 20:32 | 2021-01-25 17:58 |
Reporter | lowlander | Assigned To | |||
Priority | urgent | Severity | major | Reproducibility | always |
Status | resolved | Resolution | fixed | ||
Product Version | 5.0 | ||||
Target Version | 5.0 | Fixed in Version | 5.0 | ||
Summary | 0017395: Respect diacritics breaks search operators | ||||
Description | When setting Search Mode to Respect diacritics / Match within words search operators like Madonna AND Justin Artist: Madonna Year: 2000 however seems unaffected by this. | ||||
Tags | No tags attached. | ||||
Fixed in build | 2296 | ||||
related to | 0005565 | closed | Ludek | Full-text search only finds prefixes (gives poor results in Oriental languages) |
related to | 0017276 | closed | Ludek | Search mode options counterintuitive |
related to | 0017396 | closed | lowlander | ..value results problem |
related to | 0017439 | closed | Ludek | Match within words and search whole words in Browser view |
|
Analyzed the code and found that the advanced searching in "Search tips" haven't been implemented at all for this search mode in course of 0005565 Implementing it for all the variants could be quite complex atm -- as this search mode isn't using SQLite's FTS (full text search engine), but SQlite's 'LIKE' statement. So as short term solution for 5.0: a) eliminate the unsupported variants from the "Search tips" tooltip (leaving the full list only when the default "Ignore Diacritics \ Match beggining of words (faster)" mode is active) Long term solution (post 5.0) b) implement all the variants of searching (complex solution) or c) eliminate the 'Respect diacritics / Match within words' altogether -- as it does not seem to be used much (though can be useful for Oriental languages like Japanese, Chinese) or d) even better communicate the limitations in tooltips |
|
a) is fixed in 5.0.0.2296 Re-opened to add at least support for 'fieldname: value' that should be low risk and easy fix for 5.0 => Fixed in 2296 |
|
Re-opened to add also the AND/OR operators, after the code review it shouldn't be that hard to implement. |
|
Added the AND/OR operators and full phrase condition searching (in double-quotes) and updated the search tips accordingly in build 2296. So the original issue is resolved. |
|
Also the whole words searching in 'Respect diacritics' mode was added in 2296 (related to 0017276) i.e. when the word is in double-quotes (like "an" to not fine "another") Or when the '[ ] Search whole words only' is checked in Options > Search |