View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0017091 | MMW 5 | DB / Backup | public | 2020-11-13 19:12 | 2022-09-14 14:33 |
| Reporter | rusty | Assigned To | |||
| Priority | high | Severity | minor | Reproducibility | always |
| Status | new | Resolution | open | ||
| Product Version | 5.0 | ||||
| Target Version | 5.2 | ||||
| Summary | 0017091: 'Restore db' shouldn't delete the current DB so easily / double-prompt the user | ||||
| Description | The current DB restore behavior is that the current DB is deleted. Although we warn the user about this, this isn't the expected behavior. Here's my understanding of what currently happens: 1 Click 'Restore from backup...' --> 'This will restore the database from a backup. Do you want to proceed?' 2 Click 'Yes' --> File chooser dialog 3 User chooses DB --> "Are you sure you want to restore database from %s? This will delete current database and MediaMonkey will be automatically restarted when finished!" ---- This can be improved to eliminate the duplicate confirmation dialogs and include 'Backup' in the workflow. e.g. 1 Click 'Restore from backup...' --> Restoring your database from a backup file will delete your current database, and replace it with data from a previous backup, restarting when complete. How do you want to proceed? [[Backup]] [Restore from backup] [Cancel] OR --> Restoring your database from a backup file will delete your current database, and replace it with data from a previous backup, restarting when complete. How do you want to proceed? (o) Backup current database and then restore (.) Delete current database and restore [Proceed] [Cancel] | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
