Thread: Sony PRS-T1 in Calibre
View Single Post
Old 01-06-2012, 01:03 PM   #355
log
...
log ought to be getting tired of karma fortunes by now.log ought to be getting tired of karma fortunes by now.log ought to be getting tired of karma fortunes by now.log ought to be getting tired of karma fortunes by now.log ought to be getting tired of karma fortunes by now.log ought to be getting tired of karma fortunes by now.log ought to be getting tired of karma fortunes by now.log ought to be getting tired of karma fortunes by now.log ought to be getting tired of karma fortunes by now.log ought to be getting tired of karma fortunes by now.log ought to be getting tired of karma fortunes by now.
 
Posts: 226
Karma: 514506
Join Date: Sep 2011
Device: Sony PRS-T1
Quote:
Originally Posted by Kolenka View Post
The issue is that there is SOMETHING about the SQLite DB that has made it unreadable to the SQLite version on the PC. But apparently what the T1 itself is using is more tolerant and can work with the DB anyhow. It may be related to the version of SQLite being used or something else.

But the reality is that when it happens, even my nice DB analysis tools that use SQLite cannot read the DB without dumping it and re-creating it. I can certainly look into trying to automate it, but I have very little free time as it is. The work I did on the driver was mostly to help jump start support on the T1, as I simply don't have the time to keep a close eye on the community. Not nearly as much as I'd like.

EDIT: It could also be due to how the T1 caches DB information, since I've seen the official app run into this "corrupt" DB as well. There is a bug with the T1 firmware where plugging it in while it is asleep will kick you out to the home screen instead of the "you are connected" screen. This creates a situation where both the T1 and the PC are reading/writing the DB at the same time. This is a recipe for problems.
Ok, this is strange. It looks like the T1 must have done something to fix the corrupt database?

I'm still using the same version of calibre where I had the issue (.832) and I just finished reading the book I was reading when I first noticed the issue, just connected to calibre, had no error message and was able to transfer a new book with no error messages.

Also FYI my previous statement with difference between select count(*) and select * might be wrong. I still get the same results with my client (Base for OSX) but I just downloaded the official command line sqlite3 client for OSX and I get the proper rows when doing a select *.

And Kolenka, you have already done so much for us T1 users by enabling the calibre support so no worries! I will at least try to get some more detailed information on why it happens on how it fixes it self by keeping copies of the dbs it happens again so we can get to the bottom of it.
log is offline   Reply With Quote