View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006140 | MMW v4 | Playlist / Search | public | 2009-11-05 00:57 | 2009-11-06 23:14 |
| Reporter | Assigned To | ||||
| Priority | urgent | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 3.1.2 | ||||
| Target Version | 3.1.2 | Fixed in Version | 3.1.2 | ||
| Summary | 0006140: Searchbar does not search Encoder and some others fields after Optimize DB action | ||||
| Description | FTS search for data in Encoder does not work. Either no or erroneous results returned. See http://www.mediamonkey.com/forum/viewtopic.php?f=6&t=44121 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1287 | ||||
|
|
Ludek, can you please have a look at this? I cannot reproduce the problem, but i want to make sure that it's not a lurking/more generalized regression. |
|
|
Don't know if it is relevant but I tested DB Maintenance recently (within the last month). If I remember correctly it rebuilds SongsText as part of the process. |
|
|
Hmmm. http://www.mediamonkey.com/forum/viewtopic.php?f=6&t=37368#p227758 Also note reference to having optimized database. |
|
|
Owyn, thanks! You've done a great observation, it is really related to the DB Maintenance where is a bug in the rebuild process of the SongsText as you proposed. It is not problem only for Encoder, but also for Publisher, Copyright, Original Lyricist. It will be fixed in the next build, but the Maintain Library -> Optimize Database (Complete) will need to be performed again in order to fix it. |
|
|
You're right--on my machine (Win7), after an Optimize database (complete) operation, searches of the encoder field (using the Searchbar) no longer work. Strangely, though, performing an optimization doesn't consistently trigger this bug. What is even weirder, is that searches using the 'Search > Basic > Any text Field' also stop working for the Encoder field (which doesn't match REIKA's experience)!! Based on the link that you provided, I suspect the problem also occurs with other fields. |
|
|
Fixed in build 1286. i.e. performing Maintain Library -> Optimize Database (Complete) with build 1286 fixes the problem. |
|
|
The bug was in the Maintain Library -> Optimize Database (Complete) process itself so for the users that used the 'Maintain Library -> Optimize Database (Complete)' in MM 3.1 the bug occurs and they need to perform again 'Maintain Library -> Optimize Database (Complete) ' to fix it. |
|
|
Is there a way to test for re-Optimization required and alert the user? |
|
|
Maybe via a small script that would compare this 2 SQL queries: => Query 1: SELECT ID FROM Songs WHERE Songs.ID IN (SELECT rowid FROM SongsText WHERE SongsText MATCH ' encoder: MediaMonkey* ') => Query 2: SELECT ID FROM Songs WHERE (Songs.Encoder like 'MediaMonkey%') the results should be same. |
|
|
Verified in 1286 |
|
|
Re-opened, because this issue still exists for 'Original Artists' and 'Original Title' fields: http://www.mediamonkey.com/forum/viewtopic.php?f=6&t=37368&st=0&sk=t&sd=a&start=15 |
|
|
Fixed in build 1287. |
|
|
Verified in 1287 for "orginalartist:elvis" (that failed in 1286). |
