View Single Post
Old 08-29-2015, 05:02 AM   #12
eenk
*carrier lost*
eenk can read faster than his screen refresheseenk can read faster than his screen refresheseenk can read faster than his screen refresheseenk can read faster than his screen refresheseenk can read faster than his screen refresheseenk can read faster than his screen refresheseenk can read faster than his screen refresheseenk can read faster than his screen refresheseenk can read faster than his screen refresheseenk can read faster than his screen refresheseenk can read faster than his screen refreshes
 
eenk's Avatar
 
Posts: 62
Karma: 14000
Join Date: Aug 2015
Location: 2001:db8:e:b00c::f00d
Device: Kobo Forma, H2O v1, Aura HD
Quote:
Originally Posted by DNSB View Post
It shouldn't take that much time to ensure that your sideloaded ebooks are all backed up and then sign out of your account, sign back in and have your Kobo ebooks resynced and sideloaded ebooks reprocessed.
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?
eenk is offline   Reply With Quote