View Single Post
Old 11-13-2015, 10:38 AM   #17
eschwartz
Ex-Helpdesk Junkie
eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.
 
eschwartz's Avatar
 
Posts: 19,421
Karma: 85400180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
Quote:
Originally Posted by HarryT View Post
Replacing a "many to 1" relationship between series and books with a "many to many" relationship is not, in itself, a difficult problem; it can be done by adding a "book/series" link table into the database. But it would involve rewriting all the queries involving books and series, and every additional "join" in a query slows it down, so if (as I believe would be the case) the number of books that are in multiple series is small, the benefit of doing this is probably questionable.
Something like that, yes.

The underlying complexity of all the various queries calibre uses is also one of the reasons why rewriting the library handling to allow you to keep your books in a mess all over the filesystem à la iTunes has been repeatedly rejected as another absolute nonstarter. But of course that also has "Design Incompatibility" going for it too.

Last edited by eschwartz; 11-13-2015 at 10:41 AM.
eschwartz is offline   Reply With Quote