Current slide {CURRENT_SLIDE} of {TOTAL_SLIDES}- Best Selling in School Textbooks & Study Guides
Current slide {CURRENT_SLIDE} of {TOTAL_SLIDES}- Save on School Textbooks & Study Guides
This book is horrible. There are numerous mistakes in his instruction, such as his examples in describing multivalued dependencies, not explaining the different types of SQL used in various DBMS (i.e Oracle uses PL/SQL) , thus leading to various errors along the way. For example, the author shows that to show a value with a concatenation you use "+" signs, but in Oracle you have to use "||". Seems small in the scheme of things, but nuances such as that are not pointed out, and what college teaches database development on MS Access? The author creates data in his databases tables to support his instruction, but in reality it would never happen. You would have to read the book to understand, but in one of his examples, he claims that the name of a store is a functional dependency on the location. Well in reality it would be a multivalued dependency because an more than one store name can exist in the same town. In largeer towns and cities, there are more than one McDonald's stores. These are just small examples, but I am trying to depict here is the inevitable confusion created with this book for those inexperienced in databases.Read full review
Below Average Book. There are many typographical errors. The editor should do a better job of proofing the text. He has rewritten it from edition 9, which allows the chapters to flow more logically. In Chapter 7, the author is confused, and breaks from the current example, and pulls regresses to an example from edition 9, which was never explained in edition 10. This is a major oversight. Typographical errors in diagrams are significant, and confuse the reader. A primary key has (1.1), and should have (1,1). He forgets important commas in programming text, which is important for the compiler (and to the student's understanding). In diagrams he misnames fields, which become evident as you read the text. If you can look elsewhere, do so.
This was one of the worst database books I own, and I own many of them. It was required for a class I took in database concepts as part of a Masters degree, and even though DBs are my business I was still forced to take the class. That being said, the book is more focused on theory than practicality. There was little about real life application and tons of redundant ramblings about database normalization. The book rambles on and on about certain concepts to the point that even I do not understand what I already know if I apply what the book says. Did I mention that it is full of errors - not many critical errors but still why would you trust a book with that many minor errors.
I had to get this book for my Database class. As many others have pointed out, the book is very theoretical. Often times the author doesn't really take into account the specifics of practical database design, but he does provide a good set of rules for general database design. It is a good basis for database classes, but further instruction is necessary for practical knowledge.
I've to buy this book because it's required in my database class. In chapter 1 and 2 I can understand it easily but in other chapters it is very hard to understand. Moreover, there're many mistakes in this book, it make me think that how does this book came out to the market. I feel terrible with this book and think it such a waste of my money. So, if you're looking for database textbook, don't buy this book. If you're looking for great quality, fast shipping and reasonable price for silver jewelry, please visit my store at http://stores.ebay.com/link-to-silver