SQL Antipatterns
Most developers aren't SQL experts, and most of the SQL that gets used is inefficient, hard to maintain, and sometimes just plain wrong. This book shows you all the common mistakes, and then leads you through the best fixes. What's more, it shows you what's behind these fixes, so you'll learn a lot about relational databases along the way.
Each chapter in this book helps you identify, explain, and correct a unique and dangerous antipattern. The four parts of the book group the antipatterns in terms of logical database design, physical database design, queries, and application development.
The chances are good that your application's database layer already contains problems such as Index Shotgun, Keyless Entry, Fear of the Unknown, and Spaghetti Query. This book will help you and your team find them. Even better, it will also show you how to fix them, and how to avoid these and other problems in the future.
SQL Antipatterns gives you a rare glimpse into an SQL expert's playbook. Now you can stamp out these common database errors once and for all.
Whatever platform or programming language you use, whether you're a junior programmer or a Ph.D., SQL Antipatterns will show you how to design and build databases, how to write better database queries, and how to integrate SQL programming with your application like an expert. You'll also learn the best and most current technology for full-text search, how to design code that is resistant to SQL injection attacks, and other techniques for success.
Very well written - concise and to the point text interspersed with both SQL and general software development bits of wisdom, followed by simple but not simplistic examples. Although I've rarely seen any of the antipatterns in practice, the greatest benefit from reading this book has been in the solution sections which always listed several approaches to thwarting the antipattern and thus never failed to gave me a new perspective on doing things.
A sound coverage of typical SQL schema mistakes, with a useful exposition of the choices available in implementing inheritance. Less useful to a practitioner than I was hoping because he shies away from taxing the reader too much - thus normal forms are vaguely explained and no precise meaning is ascribed to them. Dinged also for nothing on de normalization and what you need to be careful about when doing tbis, after all de normalization can look like an anti pattern.
Great examples and very well written.I am sure that I will get back to the examples during future discussions.
As someone struggling to design my website's database, this book hit the spot. I couldn't have imagined all the things I had wrong. I'm so glad I found this gem.
The book was easy to read and well explained. However, I haven't seen very many of his anti-patterns in practice with actual projects that I've worked on in the past. Maybe I'm just lucky to work on things that were well built or I'm more experienced than the target audience for the book. However, I didn't learn too much that I didn't already know.
In the world of SQL you can do many mistakes. This will not only result in slow queries but in hours wasted to figure out what you try to achieve. Bill Karwin collected the most uses anti-patterns and explains how you can do a better job. His solutions are not only shorter to write and faster to execute, but they are simpler to maintain as well. The catalogue of anti-patterns follows a bit the one from Refactoring: Improving the Design of Existing CodeRefactoring in which every (anti-) pattern
Bill Karwin
Paperback | Pages: 328 pages Rating: 3.98 | 370 Users | 47 Reviews
Identify Of Books SQL Antipatterns
Title | : | SQL Antipatterns |
Author | : | Bill Karwin |
Book Format | : | Paperback |
Book Edition | : | First Edition |
Pages | : | Pages: 328 pages |
Published | : | July 2nd 2010 by Pragmatic Bookshelf (first published June 25th 2010) |
Categories | : | Computer Science. Programming. Science. Technology. Technical. Software |
Chronicle In Favor Of Books SQL Antipatterns
Bill Karwin has helped thousands of people write better SQL and build stronger relational databases. Now he's sharing his collection of antipatterns--the most common errors he's identified in those thousands of requests for help.Most developers aren't SQL experts, and most of the SQL that gets used is inefficient, hard to maintain, and sometimes just plain wrong. This book shows you all the common mistakes, and then leads you through the best fixes. What's more, it shows you what's behind these fixes, so you'll learn a lot about relational databases along the way.
Each chapter in this book helps you identify, explain, and correct a unique and dangerous antipattern. The four parts of the book group the antipatterns in terms of logical database design, physical database design, queries, and application development.
The chances are good that your application's database layer already contains problems such as Index Shotgun, Keyless Entry, Fear of the Unknown, and Spaghetti Query. This book will help you and your team find them. Even better, it will also show you how to fix them, and how to avoid these and other problems in the future.
SQL Antipatterns gives you a rare glimpse into an SQL expert's playbook. Now you can stamp out these common database errors once and for all.
Whatever platform or programming language you use, whether you're a junior programmer or a Ph.D., SQL Antipatterns will show you how to design and build databases, how to write better database queries, and how to integrate SQL programming with your application like an expert. You'll also learn the best and most current technology for full-text search, how to design code that is resistant to SQL injection attacks, and other techniques for success.
Specify Books As SQL Antipatterns
ISBN: | 1934356557 (ISBN13: 9781934356555) |
Edition Language: | English |
Rating Of Books SQL Antipatterns
Ratings: 3.98 From 370 Users | 47 ReviewsAssess Of Books SQL Antipatterns
I'm a software developer who gets paid mostly for working on the back end portion of solutions and I've worked in both small and large companies. I am not an SQL guru and I am more than happy to let somebody else review and fine tune any SQL that the solution uses. If I'm lucky, I'll be working in an organization large enough to have full-time SQL experts who can help me out. More times than not, however, the development team has to craft the SQL ourselves. As of late, I've been lettingVery well written - concise and to the point text interspersed with both SQL and general software development bits of wisdom, followed by simple but not simplistic examples. Although I've rarely seen any of the antipatterns in practice, the greatest benefit from reading this book has been in the solution sections which always listed several approaches to thwarting the antipattern and thus never failed to gave me a new perspective on doing things.
A sound coverage of typical SQL schema mistakes, with a useful exposition of the choices available in implementing inheritance. Less useful to a practitioner than I was hoping because he shies away from taxing the reader too much - thus normal forms are vaguely explained and no precise meaning is ascribed to them. Dinged also for nothing on de normalization and what you need to be careful about when doing tbis, after all de normalization can look like an anti pattern.
Great examples and very well written.I am sure that I will get back to the examples during future discussions.
As someone struggling to design my website's database, this book hit the spot. I couldn't have imagined all the things I had wrong. I'm so glad I found this gem.
The book was easy to read and well explained. However, I haven't seen very many of his anti-patterns in practice with actual projects that I've worked on in the past. Maybe I'm just lucky to work on things that were well built or I'm more experienced than the target audience for the book. However, I didn't learn too much that I didn't already know.
In the world of SQL you can do many mistakes. This will not only result in slow queries but in hours wasted to figure out what you try to achieve. Bill Karwin collected the most uses anti-patterns and explains how you can do a better job. His solutions are not only shorter to write and faster to execute, but they are simpler to maintain as well. The catalogue of anti-patterns follows a bit the one from Refactoring: Improving the Design of Existing CodeRefactoring in which every (anti-) pattern
0 comments:
Post a Comment
Note: Only a member of this blog may post a comment.