Quote:
Originally Posted by Jellby
|
The settings will be deleted. The device does a good job of cleaning up the database when you deleted a book. Rows in the Event table should be the only ones left.
Deleting the Events might be a bit harder. I did some fiddling a little while ago for an unrelated reason. When I deleted some Event records, the total hours read suddenly became zero. I think deleting some will be safe, and it's possible the total hours is recalculated when the next book is finished. If so, it all should be OK.
Another delete I want is to remove the full size cover. I hadn't realised that this was generated for each book when the smaller covers are generated. It's obvious now that I think of it, but it hadn't occurred to me. Removing the full size covers for all books will save a lot of space. Assuming they are regenerated when needed. If this work, I'll probably add an option to the driver to only send the thumbnail images.
Quote:
|
- Warning/abort if new filename for a book is different from the old existing filename (due to change in metadata, or templates, or internal routines)
|
That has been in the back of my mind for a long time. I haven't been happy with anything I have come up with. Ideally it would be the driver, but I can't see where to step in and do that. I might be able to do something in the plugin that wraps it.
Unfortunately, none of those are going to happen soon.