Firstly, Terisa and Helen have it right: using calibre to delete a book will remove the database entries on the device, but sending one does not add them.
Why? Because adding the database entries is harder than deleting them. To remove the book, I simply delete the rows in various tables. Over time, I have had to change this. Kobo have added tables and I missed some in my earlier passes. Adding the rows is a completely different thing. Not only do I need to know which rows to add, I also need to know the values to used. There are values in the content table that I have no idea what they mean. jgoguen tried to do this while developing the extended driver, but gave up after a while. In fact, I think he decided having a baby was easier.
So, I leave adding the book to the database to Kobo. Calibre will send the book, but you need to disconnect and let the device process it before the plugin can restore the reading position or the driver can set the series info.
Quote:
Originally Posted by auspex
I think I know the answer, but it leads me to suspect the plugin is misbehaving. When I delete a book, I see the plugin issue the SQL to clean up the database, but surely if you just delete the book, it will get cleaned up by the Kobo when I unplug the USB. And that way, there's a chance that restoring a bookmark may actually work without cycling the USB (not, of course, if changes to the driver settings or a manual request to store to a different card result in the filename changing).
|
I think that the current firmware will clean up the database when you book file is is removed. But, that definitely wasn't the case in the past. I'll check, but I will probably keep the current behaviour.
But, I'm not sure what you are saying. Delete the book, don't change the database, send the new reading position and then disconnect? That would result in no book on the device and probably no database entries. There is no point in restoring the reading position if you also remove the book. Or have I missed something?
If the point was you want to send a updated copy of the book, then that works depending on the changes. If there are no structure changes (spelling, grammar, or style changes), then just send it. The driver replaces the file and fixes the filesize in the database so the device doesn't see the change. But, if there is structure changes (TOC, file names in the book), then you need to delete the book and send it new. The device doesn't reprocess books for these sort of changes.