View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0016932 | MMW 5 | DB / Backup | public | 2020-09-19 00:20 | 2020-09-25 21:45 |
| Reporter | peke | Assigned To | |||
| Priority | immediate | Severity | feature | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Target Version | 5.0 | Fixed in Version | 5.0 | ||
| Summary | 0016932: Malformed DB: In case of malformed DB error We should offer user to Rebuild DB | ||||
| Description | As talked offline and testing on my Supplied DB I can confirm that rebuild DB fixes the malformation error (11,11) for such affected DBs. Current behavior is that MM5 constantly shows Malformed DB error (sometimes multiple ones on top of each other. As we have never been able to replicate malform (except buy physically damage DB in HEX editor, I would suggest to add option that after multiple repeated errors Mm5 suggest Rebuild DB and if user select auto close error dialogs and perform rebuild which should fix it. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 2268 | ||||
|
|
Please triage it for 5.0 as Localization strings are not yet concluded. |
|
|
In the source code I see that the mechanism for auto-fix already exists and uses existing string: "'The database seems to be corrupted. Attempt to fix it ?'" It just did not popped up in your case for some reason, to be found why... |
|
|
Fixed in 2268 |
|
|
Verified 2268 Verified Rebuild is offered and successful. |
