Quote:
Originally Posted by BetterRed
Calibre stores the series index in the book table, Octary stores it in the book-series intersection table… this facilitates many-to-many relationships between books and series - like calibre provides for Authors and Tags.
|
So Yes and No.
Yes calibre store the series index into the main book table, but also No because it store it into a "book-series intersection table" too. And store it into "book-series intersection table" is the behavior for custom series.
My guess is that the series index in the book table is a legacy data and that Kovid still not remove for reason.
The real limitations is that Calibre allow only a unique instance of book_id by intersection table, because each "book-series intersection table" and "series name table" pair is connected to a column field.
When Octary use a single pair of "book-series intersection table" and "series name table" for it entire library, without taking into account of uniqueness of book_id in the intersection table, and seem determines wich one is the main or subseries by store it in a other thrid table (not sure of that, you shared example library don't contain such data but extrapolated from the db architecture)
I don't know how Octary render the fact that a book have several series attached to it, but the very table nature of Calibre (one cell, one value) lead to the current and relevant behavior.