Quote:
Originally Posted by neil_swann80
I'm not sure what 1447LL refers to, as the book_id in the explorer-3.db file are all purely numerical and should definitely be unique.
....
FYI: Also try this logger command instead:
Code:
logger.info("Syncing to page " .. tonumber(data.page) .. " of book_id " .. tonumber(book_id) .. " with filename: " .. tostring(data.file) .. "")
|
Ok, had a closer look into it, bringing both databases to the computer and inspecting them with
sqlitebrowser, and also printing out more information as you suggested. So, my databases look at first glance sane; 1477 is the actual
book_settings/bookid =
books_impl/id of one of my books whose percentage updates correctly, whereas 14
47 is the id of one which doesn't (here I mixed up, sorry).
Of course there numbers are entirely particular of the set of books I have loaded on my reader throughout its history. But the point is: the books which stay put at 100% have
book_settings/complete=1 even if they have
book_settings/cpage <
book_settings/npage in explorer-3.db, even if I have opened them last in koreader and paged them to what is reported as cpage.
complete in turn comes (line 50-52) from self.ui.doc_settings:readSetting("summary"), i.e. from koreader itself.
It looks that once completed, forever completed, systematically for other books as well. I don't know whether to consider this a bug or a feature. In the back of my mind I think I read something about a recent change about flagging the book as completed in koreader.
ETA: ah, oh yes: in koreader, Book Status/Mark as finished... Once set back to Mark as reading I get the expected percentage in the librarian.