Feature #2440
Recovery option
| Status: | Resolved | Start date: | 01/23/2012 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 100% |
|
| Category: | - | Spent time: | 8.50 hours | |
| Target version: | Kadu - 0.12.0 | Estimated time: | 9.00 hours | |
| Fixed in Git commit: | 0079ca1b0e3a75d83e91d793abd013a4de65eff8 | Additional information: | ||
| Junior job: | No |
Description
We should provide recovery option for history (it should work automatically).
On linux it is as simple as calling:
echo ".dump" | sqlite3 old-history.db | sqlite3 new-history.db
and then renaming files.
History
Updated by Rafał Malinowski over 1 year ago
- Estimated time set to 9.00
We need:
1. to know if history file is damaged (1h) and if we can fix it (sqlite3 binary is available) (1h)
2. to ask user if history file should be recovered
3. to show new progress window with 'details' button like in some installers (3h)
4. to implement executing pipeline that fixes the file (1h)
5. and do proper renaming with all condition checks and fixes - like proper rights to everthing (3h)
Updated by Rafał Malinowski over 1 year ago
- Status changed from New to In Progress
Updated by Rafał Malinowski over 1 year ago
- % Done changed from 0 to 30
Updated by Rafał Malinowski over 1 year ago
- % Done changed from 30 to 60
Updated by Rafał Malinowski over 1 year ago
- Status changed from In Progress to Resolved
- % Done changed from 60 to 100
- Fixed in Git commit set to a6184657b538a727b1bd7752be4ee0617a0398af
Updated by Rafał Malinowski over 1 year ago
- Fixed in Git commit changed from a6184657b538a727b1bd7752be4ee0617a0398af to 0079ca1b0e3a75d83e91d793abd013a4de65eff8