Thread: Questions 902 Pro
View Single Post
Old 11-30-2010, 10:01 AM   #7
Roos
Groupie
Roos ought to be getting tired of karma fortunes by now.Roos ought to be getting tired of karma fortunes by now.Roos ought to be getting tired of karma fortunes by now.Roos ought to be getting tired of karma fortunes by now.Roos ought to be getting tired of karma fortunes by now.Roos ought to be getting tired of karma fortunes by now.Roos ought to be getting tired of karma fortunes by now.Roos ought to be getting tired of karma fortunes by now.Roos ought to be getting tired of karma fortunes by now.Roos ought to be getting tired of karma fortunes by now.Roos ought to be getting tired of karma fortunes by now.
 
Roos's Avatar
 
Posts: 182
Karma: 2371918
Join Date: Sep 2009
Location: Almere, Nederland
Device: Kindle Paperwhite, Kindle Scribe, Phone
Quote:
Originally Posted by fjtorres View Post
Why?
Oh, that's easy to answer.
Because the library datastore is the actual filesystem of the device, not a database.
Kobo stores its books in a database.
(See its reviews and forum for the downside of using a database as an ebook library. )
Basically it comes down to performance: you can either use the filesystem as a datastore and have total control over how to organize your books or use a flatfile database that gives you some sorting and tagging but dumps all the books in the same location. Either will give decent performance. Try to run a full, flexible database and performance will tank. Plus the books will be hidden from the outside.

Guys, we're talking 533MHz ARM cellphone processors in these things; not GHz-class intel Core with a GPU on the side.
Ok, i buy that for the moment, but (hey, seen that one coming eh?) the library browses on book title, that is not a file name, that is a epub internal piece of data, so why not use also the other internal pieces as options?
Roos is offline   Reply With Quote