View Single Post
Old 09-28-2013, 06:10 AM   #14
BetterRed
null operator (he/him)
BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.
 
Posts: 21,829
Karma: 30277270
Join Date: Mar 2012
Location: Sydney Australia
Device: none
Quote:
Originally Posted by DoctorOhh View Post
Calibre reduced the length used for filenames (?) when moving to the new database backend. Many folks commented on it at the time. I don't recall the details because I don't care, but it was done.
Yes I recall the discussions and I recall thinking --- hmmm, I've not noticed any change, maybe that's because I have the author and title related settings at the factory defaults. However my backup logs reveal that thousands of my library folders and format files haven't been synched for a year or more.

But this probably because I avoid using long names in the first instance, if there's going to be any shortening of folder or file names I prefer to apply my domain knowledge to do it, rather than leave it to a mechanistic algorithm.

When I add a book the first thing I do is to get the author names and title 'right', in doing that I look at the names of the folders and files created, if necessary I make changes so that the folder and file names are 'sensible'.

Quote:
Originally Posted by kacir View Post
You do not HAVE to type it that way. You can simply type....
The OP already covered that point, in post #5 MelBr wrote the following

Quote:
Originally Posted by MelBr View Post
And to answer your question: I copy/pasted the title of a book. It differed from the one inside of Calibre by a hyphen.
Before critiquing a critic one has a duty of care to oneself to read what the critic actually wrote** - its amazes me how often that maxim is ignored at Mobileread.

** I forget who said that, might have been Chesterton or Pauline Kale, Oliver Cromwell put it this way - I beseech you, in the bowels of Christ, think it possible that you may be mistaken.

But the gist of your post does go to the nub of MelBR's issue.

Calibre's 'search facility' is primarily based on querying its heavily indexed relational database, which contains structured data. I know there are Comments and similar columns - but inclusion of them in a calibre search can have a dramatic deleterious impact on search times - as in minutes rather than a couple of seconds.

However MelBR compares calibre to facilities found on search sites such as Google and sites that use Lucene. But I suspect MelBR knows full well that the techniques used to index structured data in a relational database (and a small single user one at that), and those used to index unstructured data on a zillion web pages and documents are not quite the same thing.

And that's why in the context of calibre I interpret the word 'search' as 'query' - because that's what it does, it interrogates a relational database using Structured Query Language.

Its also why I will continue to use my OS for my real searches, I almost always want to search beyond my calibre libraries, I want to see emails, letters, receipts, invoices, blog posts, media transcripts etc, etc. I don't expect calibre to find those things any more than I expect Quod Libet (music library) to find pictures of my cat.

BR

Last edited by BetterRed; 09-28-2013 at 06:21 AM.
BetterRed is offline   Reply With Quote