View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0008835 | MMW v4 | Other | public | 2011-12-08 16:42 | 2012-06-21 16:11 |
Reporter | lowlander | Assigned To | |||
Priority | urgent | Severity | minor | Reproducibility | have not tried |
Status | assigned | Resolution | open | ||
Product Version | 4.0 | ||||
Target Version | 4.1 | ||||
Summary | 0008835: Clear Library fails for very large databases | ||||
Description | When using Clear Library some AV's were thrown. It seems Clear DB does clearing of DB through SQL, wouldn't it be faster to copy clean DB to DB location? | ||||
Additional Information | http://www.mediamonkey.com/forum/viewtopic.php?f=1&t=62538 | ||||
Tags | No tags attached. | ||||
Fixed in build | |||||
related to | 0006039 | closed | Ludek | 'Clear Library' action should not delete devices |
related to | 0005836 | closed | Ludek | Clear Library loses Auto-sync [X] Playlists and [X] All Music |
related to | 0005631 | closed | Ludek | It is not clear what "Clear Library" is going to do |
related to | 0008834 | closed | Ludek | Clear Library dialog mentions Filters instead of Collections |
|
This issue is not reproducable for me even with the attached DB that is very large. e.g. the attached one has more than 1GB and thus MediaMonkey freezes in this case as the operation is performed in main thread. It would be faster to copy just clean DB, but we cannot do this because of info that needs to persist after the clear library operation - like tables Devices (0006039), custom script tables etc. But a faster solution could be with the following workflow: 1. Create clean DB (to another location) 2. Copy needed tables from old DB into new DB. 3. Request MM restart and use the new DB, the old is removed The problem just is that we cannot know which cutom stripts tables should be copied and which shouldn't. So we probably should copy all tables except for the tables that are deleted by SQL commands in the current workflow. Not sure it should be targeted as 4.0.1 though. |
|
A) Even AV logs and debug log don't show why this happened? Anything else I can do to help find the cause? B) It would be nice if Clear Library could also wipe script databases (optionally). Ideally Clear Library would offer what to remove (Files, AutoPlaylist rules, Collections, Device Info, Podcasts, Custom data, or ect.) C) For custom script tables maybe there should be a way to register what scripts are adding and have the ability to remove them on uninstall and/or Clear Library. For 4.0.1 the bug (if possible) should be removed, any underlying changes to Clear Library should be postponed to 4.1 (preferred) or after. |