Quote:
Originally Posted by log
Thanks kovid, there actually might be a problem, just haven't noticed anything on my reader yet.
When I do select count(*) from books, I get 45, when I do select * from books I get only 5 rows back. Maybe it really is corrupted?
|
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.