This week's book giveaway is in the Java in General forum. We're giving away four copies of Beginning Java 17 Fundamentals: Object-Oriented Programming in Java 17 and have ishori Sharan & Adam L Davis on-line! See this thread for details.
I'm curious if you have a view on the appropriateness (or otherwise) of Hibernate's effect on database design? The Hibernate team are adamant that valid ER design models can be arrived at working from the object model and imposing this on the database, and they suggest such things as table-per-class-hierarchy as valid choices for your ER design. This seems to me to be at direct odds with traditional ER modelling, introducing redundancy and weakening data constraints. Does your book cover using Hibernate as a driver for data model design?
The book approaches data modeling really from the same approach that we (the authors) approach it. We don't really do much discussion about the indepth theory of data/ER modeling either. Hibernate in Action has, in my opinion, already sufficiently covered the ORM theory ground.
Most of the examples we work from are Object->Database. We start with the object model, then generate the mapping schema and database tables. Obviously, we need to impose some sort of sanity and not do crazy irrational and poorly normalized database schemas, but from our perspective as non-DBA's it seems to work pretty well.