Couple comments...
Quote:
Originally Posted by chaley
I am not worried about hacking the database, beyond some experimentation to determine what the fields actually mean. I am more concerned about things like:
- time zone management. Current sony devices do very strange things with timestamps and timezones, usually resulting in throwing away the info in the database.
|
Fair point. Timestamps seem to be a count of seconds/milliseconds/ticks from some epoch. Not sure which one yet. Kinda hoping it is the standard *nix epoch, but I haven't done the math to find out.
Quote:
Originally Posted by chaley
- Resetting their reader app. There might be issues with getting the device to actually re-read the database. For example, you must actually reboot a kindle to get it to read changes to the collection database. I truly hope that Sony hasn't done something equally silly.
|
Good news here. No problems. I manually created a collection and added books to it. Unplugged the device and the new collection was available instantly. Even before it went through it's refresh. Looks like the SQLite DB is queried as needed (like when the home screen is displayed). Smart move on their part, IMO.
Quote:
Originally Posted by chaley
- Interactions with the device's book management. I have had difficulties in the past trying to convince the Sony not to reread metadata from books when the DB changes. This is similar to the timezone problem.
|
Another fair point. It looks like the Sony still does a rescan every time you unplug. It can't be re-reading all the metadata, so I'd have to assume the timestamps in the books table are key for this.
Quote:
Originally Posted by chaley
- Collection management of removable memory. You allude to this problem.
|
Yeup, two DB files. One for the SD card, one for main memory. Looks like collections that appear in each DB actually appear twice in the collections list. That's a regression in behavior. It used to merge the two into one list if I remember correctly. Since they are SQLite DBs, that means each one is self-sufficient.
Quote:
Originally Posted by chaley
- Android partition protection may get in the way, but I am less concerned about this because the Sony app must be able to talk to the database.
- Interactions with Sony software. My biggest concern here is any over-the-air purchase features they might have added.
Have fun.  |
Doesn't look like either of these will be a problem. I'm not noticing anything specific related to OTA purchase features. At least not anything new to the T1 that wasn't already part of the 900/950 models, or somewhat irrelevant to Calibre at this point. Are there any specific concerns you can think of that I might not be thinking about?
Part of what makes it take time is the inheritance that plugins have. While somewhat documented, inheritance tends to mask what a plugin really does. So it takes longer for the bigger picture to snap into focus. At least the thumbnail paths make sense now. The path just points into the cache, into a folder whose name is the id # for the row in the book table. So if a book has an _id of 89, then the thumbnail will be under the 89 folder in the cache folder. That makes it fairly easy to figure out where to put a thumbnail without clashing with Sony's software.