- Series: Pragmatic Programmers
- Paperback: 328 pages
- Publisher: Pragmatic Bookshelf; 1 edition (July 5, 2010)
- Language: English
- ISBN-10: 1934356557
- ISBN-13: 978-1934356555
- Product Dimensions: 7.5 x 1 x 9.2 inches
- Shipping Weight: 1.2 pounds (View shipping rates and policies)
- Average Customer Review: 49 customer reviews
- Amazon Best Sellers Rank: #249,212 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
SQL Antipatterns: Avoiding the Pitfalls of Database Programming (Pragmatic Programmers) 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
The Amazon Book Review
Author interviews, book reviews, editors picks, and more. Read it now
Frequently bought together
Customers who bought this item also bought
"This book is obviously the product of many years of practical experience with SQL databases. Each topic is covered in great depth, and the attention to detail in the book was beyond my expectations. Although it’s not a beginner’s book, any developer with a reasonable amount of SQL experience should find it to be a valuable reference and would be hard-pressed not to learn something new."
"Bill has written an engaging, useful, important, and unique book. Software developers will certainly benefit from reading the antipatterns and solutions described here. I immediately applied techniques from this book and improved my applications. Fantastic work!"
About the Author
Bill Karwin has been a software engineer for over twenty years, developing and supporting applications, libraries, and servers such as Zend Framework for PHP 5, the InterBase relational database, and the Enhydra Java application server. Throughout his career, Bill has shared his knowledge to help other programmers achieve success and productivity. Bill has answered thousands of questions, giving him a unique perspective on SQL mistakes that most commonly cause problems.
Browse award-winning titles. See more
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
The tips are very useful.
Especially for developers who came to databases through modern web-frameworks (though not all tips are easy to be implied in that case).
Every chapter shows wrong way, then several alternatives (from the worse to the best).
The main ideas that pervade all the chapters were
let the database do its work;don't implement its main features in software, and consequently leverage foreign keys.
My only drawback is that the book wanders off sql ground a bit too easily in the final chapters.i found the discussion of Active Record to be need more justification and depth. Otherwise, it would have been better to leave it out of this book. Similarly with the PHP examples.
I am currently studying and training to take (and pass) a Microsoft SQL Server developers certification exam. I'm using the book "Murach's SQL Server 2008 for developers" as a study and training guide. While searching for a book that delves deeper into the subject of database design and normalization, I managed to stumble across your excellent book. After spending some time reading your first chapter, "Jaywalking," I made an instant on-the-spot decision to buy your book.
It occurs to me that I might as well learn MySQL concurrently with SQL Server since the two dialects have much in common. Also, your "Antipatterns" book appears to be one of the best practical treatises on the subject of normalization and database design currently on the market, so it just makes sense to load up your bug tracking example database (on my SQL Server Express instance) and intensively study your book in lieu of the limited material on normalization and database design in the Murach book. I'm not a genius, but it occurs to me that sound database design is the key to everything else. With a good [properly normalized] database structure, queries, views, et cetera ... are more efficient and easier to build, design, and maintain. Your book is very good at making this clear. (Actually, I think of your book as a treasure trove of good information.)
In particular it just didn't cover enough ground on avoiding writing bad queries which is where a lot of anti-patterns in SQL make their way into production code.
Most recent customer reviews
Working with an SQL DB, buy it