https://bugs.kde.org/show_bug.cgi?id=523684
Ivan Čukić <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |ASSIGNED --- Comment #2 from Ivan Čukić <[email protected]> --- This is a great idea. The current system tries to restore a backup when it detects a corruption. This would be even a one step extra (and better corruption detection). The main issue I see is that this needs to be coordinated between the activities service and the users of activities-stats library. Users tend to be read-only and they do not try to detect corrupted DB at this point. Probably the correct approach here would be - clients test the integrity on start, ignore database events if corrupted - service tests the integrity on start, restore the backup or try to fix, or report the error to the user - service sends an event to the clients that the database file has been changed so that the clients reconnect. -- You are receiving this mail because: You are watching all bug changes.
