View Single Post
Old 08-31-2011, 09:05 PM   #18
therealjoeblow
Zealot
therealjoeblow reads XML... blindfoldedtherealjoeblow reads XML... blindfoldedtherealjoeblow reads XML... blindfoldedtherealjoeblow reads XML... blindfoldedtherealjoeblow reads XML... blindfoldedtherealjoeblow reads XML... blindfoldedtherealjoeblow reads XML... blindfoldedtherealjoeblow reads XML... blindfoldedtherealjoeblow reads XML... blindfoldedtherealjoeblow reads XML... blindfoldedtherealjoeblow reads XML... blindfolded
 
Posts: 106
Karma: 52102
Join Date: Jun 2010
Device: Samsung Android Tablet w/Moon+ Pro Reader
Quote:
Originally Posted by FJames View Post
This error message is most likely reporting that the SQLite database tables have been corrupted, a problem that could result from many different causes (e.g., a power failure or unexpected disconnect while updating the tables). Some people seem to get this error frequently, while others never get it, so it's likely resulting from some hardware difference like a bad USB cable or connector, or some critical difference in procedure that nobody has figured out yet. The other thread has some speculation on possible software/procedural causes, but I'd put my money on the USB connector or cable, since I've seen many reports of bad micro-USB connectors or cables.
I don't care what the problem is frankly - any 1st year computer science student learns that when programming a database, you need to build in redundancy and error recovery. If there's a problem with one single record, you do NOT corrupt the whole database and require everything to be wiped and factory reset.

You simply refuse to add the bad record and report an error back to the user so that they know which one is bad and can fix it.

And when writing to the database, you never do it live to a whole file so it can get trashed during any electrical glitch - you make a copy, write to the original, check the file, and after all is good, then delete the backup. And if anything isn't good, you copy the backup back over the original and start again, so you're never without a safe copy of the previously known good records.

And if the problem lies with the file system or OS instead of the databbase, well, those problems have been licked years ago too by smart people. I haven't had to reinstall Windows because of a corrupted FS or OS since the Win95 days! And Linux is even more bulletproof.

Simple comp-sci 101, and Kobo dev's FAILED miserably here!

As I said in another post, this problem does NOT occur with MP3 players, smart phones with USB mass storage capability or flash drives, so Kobo is obviously doing something terribly unique and wrong.

Cheers
The REAL Joe
therealjoeblow is offline   Reply With Quote