View Single Post
Old 05-08-2013, 06:04 PM   #7
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,791
Karma: 30237628
Join Date: Mar 2012
Location: Sydney Australia
Device: none
Quote:
Originally Posted by emanuensis View Post
There are at least 4 naming violations Calibre forces: 1) the creation of an extra layer as you mentioned 2) the creation of a folder with a blank in it 3) missed case names 4) names over 255 characters in length. All of these cause various types of headaches.
The use of the word 'violation' implies that there exists a written de-facto statute.

Item 1 - extra layers of ??? is a design issue, there are no de-facto design standards in the field of software engineering. There are various de-jure conventions based on various 'models and theories' but they are as hotly contested as similar things are in the world of economics.

AFAIK items 2, 3 and 4 are governed by the Institute of Electrical and Electronics Engineers (IEEE) standards known as POSIX (Portable Operating System Interface). To my knowledge, POSIX does not mandate that file system object names cannot have spaces, nor does it mandate that they cannot have mixed case and its mandated maximum path length is 32K bytes.

Quote:
Originally Posted by emanuensis View Post
DB approaches which work on blobs are only useful (for hefty home sized computers) to about 10^5. my library is approaching 10^6 and it is necessary to find a higher level of organization. At the high end they take too long, and are thus increasingly vulnerable to faults. Though often (unfortunately for safety not always) the faults are repairable, this again takes time. Calibre makes it difficult, as more than one instance cannot be run in the same operating system. Not even the "portable" version.
The only data I can imagine that your suggesting Calibre might store as database BLOBs are the book cover image and the actual book in what ever format(s) you have it.

But the fact is, Calibre does not store those things in its database, they are stored as regular files in the host operating systems (Windows, OS/X, Linux) file system (NTFS, HFS+, Ext3 etc).

It may be that it is the database technology used by Calibre (SQLlite) that prevents the execution of more than instance of Calibre. But that has nothing to do with BLOB's — I don't know for certain that SQLite is the roadblock, I maybe maligning an innocent party, barking up the wrong tree, whatever...

BR
BetterRed is online now   Reply With Quote