View Single Post
Old 08-16-2014, 05:42 AM   #30
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by chrisridd View Post
I haven't looked much at what goes in the DB, aside from there being one row in it for each encrypted file in each protected book.
I said earlier:
Quote:
Originally Posted by davidfor View Post
  • Database records - one row for the book (containing the metadata including the description), two rows for each chapter in the book, one row for each collection the book is in. Exactly how much space depends on the comments in the metadata and the number of chapters, but it shouldn't exceed 100KB. More rows will be added as you read and if you add bookmarks/annotations.
Because the OP was coming from a Sony, I assumed they were comparing sideloaded epubs. For kepubs, there is an extra row per chapter/file in the book. And if the kepub has DRM, there is another row for each encrypted file in the kepub. And of course there are indexes and other database overhead that I didn't mention before. But, would still be surprised if it is more than 100KB per book.
davidfor is offline   Reply With Quote