Quote:
Originally Posted by johnnyb
Moreover, spontaneously corrupting databases are not unheard of in the Kobo realm, so that would help with that...
|
Well, not quite spontaneously, at least not in my experience -- you do have to do something wrong, as an user, to cause a corruption. The problem with the Kobo database is that it's so susceptible to it that even disconnecting the device from the USB port without ejecting it first, or without waiting for the ejection process to be over, can be fatal (in fact I've had a grand total of two database corruptions in 5 years, one happening as explained above, one by tampering with the software on purpose). This is something that most users don't even think about, or remember -- how many people just disconnect their USB drives without anything ever happening? What if your USB cable is not inserted properly? 99% of the time it's fine, usually, but with the Kobo ereaders you'd have to lower that estimate quite a bit. And so people don't realise that they've caused a corruption, and won't even find out that their database is corrupted if they don't use calibre and the right plugins to check its integrity, and when their ereaders start acting up they don't know the reason. Perhaps Kobo, besides working on preventing database corruption, could at least work into the software some kind of warning message that pops out whenever the database gets corrupt, urging the user to sign out of the readers so that it can be recreated.
Oops, this turned into a rant -- didn't mean to, sorry.