Quote:
Originally Posted by theducks
I can see a use for table specific 'Custom columns' (Authors in this case).
The Issue is 'user support'  How many of Calibre Users know that Calibre is not a 'Flat File'? |
How many users of internet banking know their bank accounts are not in a flat file, and how many care.
Quote:
Originally Posted by theducks
 Now try and explain why you attach the Column to 'authors' and not 'books_authors_lnk' |
Why on earth would a user want to know about what foreign keys are defined in what tables.
Quote:
Originally Posted by theducks
Forgetting those user issues 
How do you support a decent UI and data integrity for these other tables  |
For UI's that support multiple entities there are several Salesforce, Patient Care, Purchasing, Help Desk etc systems from which ideas might be drawn.
As for database integrity, why would one not apply the same techniques and disciplines as are already used in Calibre. There's already somewhere to store the author metadata backup files - as an xml file in the Author folders - same as the opf files in Book folders.
I am NOT saying its easy, nor that it wouldn't be quite a lot of work - but lets not pretend its rocket science
BR