View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0019578 | MediaMonkey 5 | DB / Backup | public | 2022-11-21 19:55 | 2022-11-29 20:09 |
| Reporter | Ludek | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | have not tried |
| Status | feedback | Resolution | open | ||
| Product Version | 5.0 | ||||
| Target Version | 5.1 | ||||
| Summary | 0019578: Improve error handling when DB cannot be accessed | ||||
| Description | Currently when DB cannot be accessed then Debug builds generates crash log -- which does not say nothing to users about the reasons. - Rusty observed 0019559 where DB couldn't be accessed because of Disk I/O error - LowLander observed crash when his M.2 drive loses drive letter. This caused MM to not have access to the DB on the drive. Looking at the errors that could be handled that way (to be shown with message dialog + Retry button): SQLITE_BUSY = 5; // The database file is locked SQLITE_LOCKED = 6; // A table in the database is locked SQLITE_READONLY = 8; // Attempt to write a readonly database SQLITE_IOERR = 10; // Some kind of disk I/O error occurred SQLITE_CANTOPEN = 14; // Unable to open the database file SQLITE_NOTADB = 26; // File opened that is not a database file I think that for all these errors we could show a common dialog like: "Database file %s cannot be accessed." "Error" <<error code>> [Retry] [Cancel] Note that "Database file %s cannot be accessed." would be a new string to translate. As "Error" already exists. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
