<< 1 >>
Rating: 
Summary: Philip Greenspun's opinion; I trust him!
Review: In our computer-obsessed society, we need not be stuck with the dry theoretical offerings of computer scientists. Walk into any bookstore and you'll find SQL tutorials. Sadly, due to structural problems in the trade computer book industry most of these books are written by authors who picked up SQL as they were writing. There are some good ones, however, our favorite being The Practical SQL Handbook (Bowman, Emerson, Darnovsky; Addison-Wesley). We truly do like this book so we can feel free to pick on it: * though it is 450 pages long, by straining to offer complete coverage of simple boring stuff the authors run out of space and energy to cover the interesting and sophisticated stuff * students have to learn SQL in the context of a data model; like its competitors The Practical SQL Handbook forces readers to live in the dessicated world of business data processing for several hundred pages. This is where the RDBMS started in the 1970s and if you want to get a job in a corporate IS department, this is not a bad place to live while learning SQL. However, we're trying to demonstrate how the concurrency control and transaction management capabilities of the RDBMS enable the construction of powerful reliable Web services. We can dazzle the students with much more interesting and relevant data models than Practical SQL's "bookbiz database about a fictitious publishing company". * the authors write with the assumption that the reader is unaccustomed to thinking formally and using formal languages * the authors avoid the ugly fact that SQL is not a standard. Most SQL queries involve dates and times. Yet there are only two pages out of 450 involving the date data type. Why? The authors don't explain but perhaps it is because they didn't want to say "here's what ANSI SQL date-time arithmetic looks like and, by the way, Oracle has completely different syntax and semantics." * the authors assume that the Web doesn't exist, i.e., that the physical book must be self-contained and comprehensive. Anyone actually using an RDBMS is going to have full documentation on the Web or at least (shudder) on CD-ROM. This book started on the Web and therefore we assume that we can cover the interesting and pedagogically valuable stuff then link students to the full documentation. Bashing other authors and publishers is fun but isn't pedagogically effective. Thus it is probably worth stating what this SQL tutorial tries to do.
Rating:
Summary: good companion book!
Review: Smart, well reasoned, and covered what I needed.
Excellent book, I development multimedia software, and use SQL, for my programs, easy to read, form mystery to mastery! this book is my head book!
Rating: 
Summary: significant limitations
Review: This book came to me with excellent references and I was eager to dive in. I found the book easy to read, and provides a good introduction. It is probably appropriate if you are doing some basic work with an existing database. However I had significant issues: - many of the examples assume you are using Sybase and won't work on other systems. This bias may come from the tied with Sybase; the book comes with a Sybase CD and two of the authors are from Sybase. - Attempts are made to point out differences between the various systems, however they seem to have been quickly added to allow for a fourth edition. The added text breaks the flow and adds confusion. - It lacks the depth for building a database or complex work.
Rating:
Summary: significant limitations
Review: This book came to me with excellent references and I was eager to dive in. I found the book easy to read, and provides a good introduction. It is probably appropriate if you are doing some basic work with an existing database. However I had significant issues: - many of the examples assume you are using Sybase and won't work on other systems. This bias may come from the tied with Sybase; the book comes with a Sybase CD and two of the authors are from Sybase. - Attempts are made to point out differences between the various systems, however they seem to have been quickly added to allow for a fourth edition. The added text breaks the flow and adds confusion. - It lacks the depth for building a database or complex work.
Rating:
Summary: good
Review: This is a good book for the people who r new to sql.
Rating:
Summary: good
Review: This is a good book for the people who r new to sql.
Rating:
Summary: Essential SQL Text Improves
Review: What makes this Fourth Edition to the Practical SQL series special is the approach to teaching SQL shared by all the editions in this series. The same statements and queries are covered by many SQL texts, but not with the same clarity or teaching philosophy. Beginning programmers are often unaware that much of programming goes according to what I like to call "programmer lore." The accumulated tradition of practices that are not written down in any book of algorithms but handed down from programmer to programmer in back rooms and online discussion groups. This largely "oral tradition" that exists within the culture of programming is essential to developing real world applications. This handed down knowledge is essential because most authors follow their own academic interests in the more theoretical while most programmers are too busy to write down daily practice. As the foreword says, the idea for this edition is to reclaim this knowledge and present it as if folk wisdom handed down from a master chef. I will not delve into the specifics of each chapter or repeat here the SQL concepts taught within, because all SQL books purport to teach the same elements. What makes this book different is the way it follows a set of principles designed to make learning easier. The explanations are clearly presented in plain language without any unexplained buzzwords or digressions into mathematical theory. With each topic, the author starts with basics then follows through with more advanced concepts in a seamless manner without condescension. The chapters concentrate on teaching how to do the things everyone needs to do, answering the frequently asked questions beginners have without cutting corners on relational principles. Practicality is the watchword where another author might be tempted to explain only idealized forms. This books fits perfectly with my philosophy of learning. The explanations take the reader from beginning to advanced level seamlessly. They do not forego advanced concepts, "dumbing down" to the perceived level of the beginner. They do not try to "protect" the beginner from advanced concepts, but explain them with the same clarity as the novice ones, using language that anyone reading a newspaper could understand. In Practical SQL, both beginning and advanced concepts get the same plain language treatment. Even advanced programmers benefit from simple, clear explanations shorn of arcane jargon and obtuse concepts. Another thing I believe in is providing copious example code for the learner. They first run to the code to see what it does, then later they can modify the code in order to expand upon it, using it as a prototype (an important concept in learning, making things your own; another is modeling, using the prototype to create your own useful tools). Practical SQL is filled with examples presented in a clear style with improved presentation. Examples are flagged by side heads and use larger type. In addition, tips appear occasionally. A lot of thought went into making the text readable and accessible. I am a heavy user of MySQL and found the previous Third Edition of Practical SQL extremely helpful in understanding complex queries as well as understanding the limits and advantages of MySQL in comparison to the features of other enterprise servers. Like the consultant who wrote the forward, I find myself picking up Practical SQL when I have trouble with a complicated query, despite having worked with SQL for several years. I expect the Fourth Edition to be no less helpful. You will not learn the details of web programming from this edition, but you will be left with a better understanding of the relational model and the language that drives your web applications. All without being required to wade through a lot of mathematical jargon. However, the author never compromises relational principles for simplification. There is no doubt that you should have this book if you work with SQL in any way.
<< 1 >>
| 
