Rating: 
Summary: A relvar by any other name.
Review: This book introduces the fundamentals of database systems by emphasizing the relational data model, and that a database is really "a collection of true .. propositions". Although his use of Tutorial-D (rather than SQL) may seem odd, Date emphasizes thinking about data rather than an implementation. This book provides great fundamental thinking about relational variables (relvars), domains, relational algebra, and data normalization.The further topic of missing information contrasts to Codd's four-valued logic, and even if your particular database system supports different Nulls the chapter helps when thinking about your own data. Whether or not you agree with his thinking about object-oriented databases, his "Two great blunders" are a challenge to any software vendor. His chapter on decision support does not provide much of an introduction to such broad topics as warehousing, OLAP, and data mining, but there are other sources. This is not an easy read, but working through it will pay off when coupled with product training.
Rating:
Summary: A relvar by any other name.
Review: This book introduces the fundamentals of database systems by emphasizing the relational data model, and that a database is really "a collection of true .. propositions". Although his use of Tutorial-D (rather than SQL) may seem odd, Date emphasizes thinking about data rather than an implementation. This book provides great fundamental thinking about relational variables (relvars), domains, relational algebra, and data normalization. The further topic of missing information contrasts to Codd's four-valued logic, and even if your particular database system supports different Nulls the chapter helps when thinking about your own data. Whether or not you agree with his thinking about object-oriented databases, his "Two great blunders" are a challenge to any software vendor. His chapter on decision support does not provide much of an introduction to such broad topics as warehousing, OLAP, and data mining, but there are other sources. This is not an easy read, but working through it will pay off when coupled with product training.
Rating: 
Summary: Terrible. So many words and so little content
Review: This book is an introduction to database systems as seen from the application developer. It covers the basics of databases (most importantly the relational databases), SQL (and variants) normal forms and many other things from ther viewpoint of the application programmer. It explains why things are done like they are. It does not provide a good guide on how to design database applications or databases, nor does it help you implement your own database system. It is mostly just a theoretical text book to give an introduction to database theory. However all in all it does contain some useful information. Unfortunately this extremely poorly written and uses far too many words to explain so little. In fact, I often found myself almost falling asleep while reading it and then missing important information when it finally was there. This book are constantly updated to new editions - and this shows in a bad way. It is full of notes, asides and footnotes and the structure is terrible. One place it has a foot note that spans over three pages. This is unacceptable! In the end I cannot recommend this book. It is way to long, not focused and extremely dull. There are much better books on databases out there. Avoid this one.
Rating:
Summary: Burn this Book
Review: This book is the worst piece of swill I have some across in awhile. There is absolutely no editing by anyone whom has any knowledge of the english language. After trudging through the first five chapters, I am thinking of having my good teeth drilled. It would be less painfull. The only good that can come of this will be my renewed faith in the church, as I will head down there this sunday with the recomendation this book be burned and the earth salted.
| 
