Quote:
Originally Posted by rkomar
In case anyone is interested, the database files are in SQLite format. You can copy the file off the device and peruse it with the sqlite3 utility. Maybe even fix it by hand if you are dedicated/crazy enough.
|
Quote:
|
Originally Posted by Elfwreck
I found a sqlite viewer to check out the database, and confirmed that (1) I have basically no idea how databases work and (2) being able to spot that, yes, new books are Not Here, does not help me figure out how or what to fix.
|
There's not that much you can do with the databases. Checking for corruption is one thing (closed transactions & integrity_check), the other seeing which books were added last. (It happens I'm interested in DB changes between firmwares, for a reading progress transfer.)
Quote:
|
Originally Posted by rkomar;
Doesn't calibre update the database when it installs ebooks on the pocketbook devices? Perhaps there are clues there about what needs to be done. Anyway, that's for someone who is comfortable with SQL. It's not a job for just anyone (including myself).
|
Only for Kobo readers (and others perhaps) the DB is modified directly.
Quote:
|
(Also wold says the databases are... hashed? Blocked from editing. Can't just go into the raw data and fix it to match the ereader's contents. I guess that makes sense; it'd be much easier to break the database than fix it that way.)
|
Not the databases, but the PB configuration files have a hashed signature. Those config files (effectively .txt files) can't be edited, only deleted or left as is. Databases can be modified at will.
This came up as your "recent items" list fails to update. Now the recent list data is stored (for me) in /system/cache/desktop/cache.dat, so deleting that, and it's .back copy, is worth a try (as you already removed newly added books).