Quote:
Originally Posted by DoctorOhh
Being ignorant in what you're facing I wonder if search couldn't be sped up with the metadata.db file being transferred to the device?
|
It might if I wrote another search engine to use directly the db. Unfortunately, calibre's search language can make that less than optimal. In particular, naked (no prefix) searches would be horrible because I would need to retrieve *all* the fields just to check if the string is in any of them. Partial matching would also be a pain, but less so. Parenthesized expressions with AND, OR, and NOT would also present difficulties to a system based on DB queries. If I gave up on using calibre's (and CC's) search language and allowed only single-question prefixed queries (queries of the form series:x or title:y) then I could quite easily search using metadata.db, but even here there is a potential problem with things like series_index.
I still remain unconvinced that search is needed, given that I am using a content-server tree-based interface. Here are some screen captures from the top-level down to a series list. Unless you are looking for something that is in the middle of an item (e.g., I want the book with "pirate" somewhere in the title) then the tree index will get you there.