View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007898 | MMW v4 | DB/FileMonitor | public | 2011-05-30 12:58 | 2011-06-13 13:37 |
| Reporter | Ludek | Assigned To | |||
| Priority | urgent | Severity | crash | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 4.0 | ||||
| Target Version | 4.0 | Fixed in Version | 4.0 | ||
| Summary | 0007898: Trying to clear database freezes MM | ||||
| Description | Tested with build 1380: 1. Go to 'File' -> 'Clear database...' 2. confirm by typing 'YES' => freeze | ||||
| Additional Information | http://www.mediamonkey.com/forum/viewtopic.php?f=6&t=58156 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1382 | ||||
|
|
I debugged the issue and it seems that SQL query 'DELETE FROM Songs' takes too long. Jiri, wouldn't it be better and safer to force the users to restart MM and start with newly created DB? |
|
|
We can't just replace the DB, because some data persist even in the new DB (e.g. Devices table). We could copy such data to the new DB, I'm sure whether it's worth the effort though. I wonder, is there any diff since MM 3? I don't think that there can be any significant slowdown, since there weren't any really big DB schema changes? |
|
|
In MM3 it was several times faster because of DB triggers that were enhanced in MM4. Nevertheless I optimized the whole procedure of clearing DB so that the tables without triggers are cleared at first. This way the whole process takes 15 seconds on my DB while it took 2 minutes with build 1381. It is even faster than with MM3. Fixed in build 1382. |
|
|
Verified 1388 |
