Quote:
Originally Posted by Stinger
timlegge,
were you able to figure out the database structure fairly completely?
I ask because I'm wondering how hard it would be to implement a new feature.
What I'm looking for is a function that would remove all residual entries from the dbase. Last time I looked at it, the dbase contained ALOT of residual entries for epubs I'd already removed, as well as residual image files for those epubs in the standard directory.
I ask here since the driver is already capable or detecting which books are actually on the Kobo, it must posses the functionality to ignore these residual entries that point at a book that's not there.
|
Actually, that is a good point. I don't think the driver makes any allowance for that. It would list the books if they exist and probably allow you to delete these ghost entires.
I did notice that some people only deleted from content and left dangling records in volume_shortcovers. I know I did and I plan to address that cleanup at some point.
The database is fairly well documented at the wiki that darkadept has at
http://wiki.durbn.net/koboko/index.php/DBSchemaV2. I figured out most of it myself and went there to post updates but realized it was pretty much all there and some of the SQL for the deletes were better than mine.
Tim