Specialization and generalization in database and application development

Is there any reason to have a specialization? If so, do you have any reason to have a generalization? It may seem obvious, but perhaps one of the two seems to be wrong in relational modeling. If you are speaking in specialization you do not have to talk about relationships, they are exclusionary concepts.

Do nothing for no reason. Ask yourself the reason to use something? What problem is this solving? And what are they being caused?

You say that each type of book has specific business rules. Really? are you sure? Let's say yes, and why are business rules in the database? Let's say you want to do so, what the question already shows that this is not a good idea, what solution do you see other than separating each type into a table? If the data behaves differently it must be in a different table. I just would not do so, within my vision, I might even need something out of the ordinary.

One solution is to have a table only and some actions that depend on the type are made conditionally.

There is no deadlock. I do not see any specialization or relationship there, so there is no dichotomy. It only has different business rules that are programmed in the application. Or in the database if you prefer. But you do not have to create a new table if the structure is the same. Database is not application, although some think it is.

See advantages and disadvantages of per the business rule in the database .

I was thinking that your book specializations might be, for example:

• Digital Books
• Audiobooks
• Printed books

in which the nature of the reading experience was different in each case. Hence a specialization would make sense.