I've not read the book so can't comment on it specifically, but I can tell you about Date, who is an eminent author in the field. His 'An Introduction to Database Systems' is perhaps the best book to read if you want to get an idea of how DBMSs work internally. Anyway:

- He really dislikes SQL (His books often use Tutorial D, which is a language Date created to represent what a good relational query language would look like).

- He really hates the use of null values.

- He's of an academic bent - dryish, but still perfectly readable.

- I would say that he tends to gloss over performance issues that get in the way of ideal database schema design, viewing them as implementation issues (which is true, but in reality, all DBMS products have weaknesses, and at some point you'll probably have to make compromises in your schema design).

With this said, I would read his book. He'll tell you the best way to do things, if you ignore performance. This puts you in a good position to start out from a pure, ideal implementation from which you can compromise when you have to. I much prefer this to a less-educated ad-hoc approach.