Thread: Kobo and Calibre
View Single Post
Old 09-04-2012, 09:55 PM   #8
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by itimpi View Post
I think this warning was introduced as the maintainer of the Kobo driver for Calibre is not currently active. This means that the driver is not being enhanced for newer Kobo firmware versions. As long as the database format does not change you are OK, but if it does this a warning that the results will be unpredicatable.
This is a good post to reply to about the Kobo Touch database.

The database has changed, but not in a way that affects the drivers interaction with it. Some new tables have been added for bookshelf support and some new columns added to the existing tables. calibre doesn't need to go near these columns. There might be an issue if the driver was trying to insert or update rows in the tables, but it doesn't. Deleting a book is the only time the driver updates the database. This is fine. It leaves the bookshelf rows behind, but the device will clean these up.

There is one issue with the new firmware that isn't there for the old firmware. The Kobo is inconsistent with how it stores dates in the database. They are actually strings but some are stored with milliseconds and some without. And some have timezone info. The different formats used seems to be related to the book format. PDFs and CBR/CBZ files can have a format that the driver doesn't expect and throws an exception. If this happens, the device list is incomplete.

But, it appears that problem has gone away. I just looked at the source for this, and it wasn't what I remembered. Looks like Kovid has put a fix in for this. It is dated 29/8 but wasn't listed in last weeks fixes. But, a quick test shows it was included and solves that issue.
davidfor is offline   Reply With Quote