View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009173 | MMW Wishlist | Install/Config | public | 2012-02-23 19:18 | 2012-02-23 19:19 |
| Reporter | lowlander | Assigned To | |||
| Priority | none | Severity | minor | Reproducibility | always |
| Status | new | Resolution | open | ||
| Summary | 0009173: Improve DB Upgrade process | ||||
| Description | Installing a Portable Install of MediaMonkey 4 on a machine with MediaMonkey 3 and existing Portable Install of MediaMonkey 4 auto-updated the MediaMonkey 3 database which was unwanted and caused problems with the existing MediaMonkey 3 install. At the very least a confirmation asking the user that DB should be upgraded is urgent as the DB Upgrade can take very long and may not be what the user wants. Much better would be the more elaborate solution proposed below. | ||||
| Steps To Reproduce | When MediaMonkey needs to upgrade the DB it should ask the user if this should be done. User would be presented with Yes, No and Cancel. - Cancel would close MediaMonkey and Cancel the DB Upgrade. - No would start the user with a clean DB. MediaMonkey would offer the following options: - Use new default DB location (rename existing DB if there) - Use old default DB location (set DBName in ini, rename existing DB file) - Use previous custom location (if one was used, rename existing DB) - Use a new custom location (user can select one, DBName is set in ini) - Yes would upgrade the existing DB - MediaMonkey would first warn user that it is recommended to use complete optimization on database prior to upgrade - Ideally it would offer to do this so user doesn't have to downgrade to accomplish this - MediaMonkey would first scan for existing MM installs and their DB's (user may have multiple versions of MM installed) - MediaMonkey would show a list all found DBs (and include their MediaMonkey version) - User would select which DB to use - MediaMonkey would offer options for the converted DB locations: - Use default DB location (rename existing DB if there) - Use old default DB location (set DBName in ini, rename existing DB file) - Use previous custom location (if one was used, rename existing DB) - Use a new custom location (user can select one, DBName is set in ini) - MediaMonkey would then proceed with DB upgrade process, this would show more information than current progress bar - Show step x of y (it seems there is a fixed amount of steps in upgrade) - Show progress in each step ie. record x of y records - On failure MediaMonkey would again inform user to do a complete optimization in the MediaMonkey version of the DB (unless it can be build in DB Upgrade process) - Failure message would offer to start user with clean DB and note that this means no track data, playlists, play history, etc. are transferred. | ||||
| Additional Information | Upgrade options should be auto-limited (lacks user control) or have a warning if replacing DB would interfere with still installed MediaMonkey versions. In other words it would verify that the DB Upgrade isn't an in-place upgrade, but that old version(s) of MediaMonkey are still installed. | ||||
| Tags | No tags attached. | ||||
