Quote:
Originally Posted by TechniSol
The other question, and it's a good one, is why are those sqlite databases so large? Based on the size reported by one poster for a given number of books they are storing 40KB on average per book? What is all that, and is it why it appears accessing the DB takes so long? That's a lot of space to store a book title, path, current page, some reading stats, and some metadata... so what else are they bogging the Db down with? If it's annotations or the like, reference them by storing a path and filename and dump them into their own text files already.
.
|
There are multiple entries for each epub (one entry per html split) with a lot of properties/flags in this database - and this in two tables: tbl_content and tbl_volume_shortcovers). That could explain the DB size increase per book. Maybe this also explains the slow updating/DB-building speed: unpacking the epub files in bulk might well take some time. (But this is just speculation since I have no idea what to expect from a Linux based device with the processing power of an ebook reader in terms of file handling).
Anyway: the database, while not elegantly designed, is still small by any standard and should be easily manageable by the device - assuming reasonable programming that is ...