Quote:
Originally Posted by eenk
So does this mean that "usually" not the SQLite database files become corrupted in themselves, but the data becomes inconsistent instead (incomplete update, programming error)? In the first case, would there be some SQLite tool that could be run on the corrupt db file trying to fix it without loosing all data?
Well, in the second case I guess that a complete db rebuild from scratch by sign out-sign in is the only viable option, right?
|
I've had databases that according to the my utilities collection (SQLite Expert Personal, DB Browser for SQLite, SQLite Studio, etc. ... what can I say? I can't resist utilities) had no issues but my Kobo ereader disagreed. Looking at the contents of the database, in several cases there were issues with the contents of several tables, as you said, inconsistent data.
I've tried several utilities to re-index, clean up and/or "repair" databases but none that gave me results that I was happy with. For the most part, I found that it was simply easier to revert back to the factory database, restore a database backup and then resync/reprocess my ebooks.
Using davidfor's Kobo Utilities with Calibre to backup the database on connect is my current preference to minimize the amount of ebooks that need to be reprocessed.