View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0016096 | MMW v4 | DB/FileMonitor | public | 2019-11-07 00:07 | 2022-08-31 17:38 |
| Reporter | peke | Assigned To | |||
| Priority | urgent | Severity | block | Reproducibility | unable to reproduce |
| Status | closed | Resolution | fixed | ||
| Target Version | 4.1.26 | Fixed in Version | 4.1.26 | ||
| Summary | 0016096: DB: DB initialization/Upgrade fail MM can't start | ||||
| Description | If MM crashes during update/init of MM.DB that left library corrupted on next start MM should check DB integrity and delete/rename MM.DB to MM.DB.Corrupted in order to either create new MM.DB or try to reimport/upgrade backup DB created during init/upgrade process. | ||||
| Additional Information | SSV-602-19043 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1896 | ||||
|
|
The problem is that "PRAGMA integrity_check;" on the user's database returns "OK" (ticket SSV-602-19043), but the database has only 97 KB, includes just one row in DBInfo table and Songs table has 10 entries where all values are NULL. Nevertheless I will add checking of DBInfo table, it must always include 4 rows (consisting of version major, minor, release and database id). If the check fails then the MM.DB will be renamed to MM.DB.corrupted and fresh MM.DB will be created. |
|
|
Added in 4.1.26.1896 and merged to 5.0.0.2212 |
|
|
Verified 2218 Close after test in 1896 |
|
|
Verified 1896 Closing |
