SQL Antipatterns, by Bill Karwin, Pragmatic Bookshelf, mention of a broad variety of databases such as MySQL, Oracle, SQL Server. Common blunders of SQL database design, queries, and software SQL Antipatterns Strike Back Bill Karwin 1 Monday, April 20, 1. Bill Karwin has helped thousands of people write better SQL and buildstronger relational databases. Now he’s sharing his collection of antipatterns–the most.
|Published (Last):||17 August 2013|
|PDF File Size:||2.84 Mb|
|ePub File Size:||7.80 Mb|
|Price:||Free* [*Free Regsitration Required]|
The final verdict is: By professional developers for professional developers. Advanced SQL programmers should know all this already. Even better, it explains in dept why they are errors antipatterbs the problems you might have because of these errors.
Antipatternsbook reviewSQL. This was a good book. This post is a review of what this book is all about and why you should be interested in reading it. Mar 29, Zlatin Stanimirov rated antipatternd really liked it. Bill Karwin has been a software engineer for over twenty years, developing and supporting applications, libraries, and servers such as Zend Framework for PHP 5the Antiatterns relational database, and the Enhydra Java application server.
It is the first book I’ve read on database design and optimization after 5 years of professional software development. A must-read for beginners, good for intermediate.
Jan 18, Bill rated it liked it. Fear of the Unknown Objective: This book shows you all the common mistakes, and then leads you through the best fixes. I just want to warn everyone reading it, to give it a chance and read the whole of it.
Book Review – SQL Antipatterns – Vlad Mihalcea
Fetch a Sample Row Antipattern: Then even if it mostly is harmful, there are situations when that pattern is the better solution. Some are mistakes I would expect only a real newbie to make.
Bill Karwin has helped thousands of people write better SQL and build stronger relational databases. See No Antipwtterns Objective: The chances are good that your application’s database layer already contains problems such as Index ShotgunKeyless EntryFear of the Unknownand Spaghetti Query. Most antipatterns are about misunderstandings on good database design; for example, the author discusses such timeless classics as implementing many-to-many relationships by putting multiple comma-separated values in a row.
Even better, it will also show you how to fix them, and how to avoid these and other problems in the future. First, this is based on B6. Declare Constraints Chapter 6: As a few examples, multi-valued columns, multi-column attributes, too many indexes, replacing null values with a different known value, etc. Oct 29, Phil Eaton rated it really liked it Shelves: The bad side is that the book is bit bloated, and the last part on application-related anti-patterns doesn’t really fit in.
Harmed with this knowledge, I should not repeat those mistakes and I should have better arguments next time someone in my team is about to commit one. If in one way or another you are involved with databases you should read this book. Having a strong background in this topic, I was able to skim through it easily in one afternoon. This book is obviously the product of many years of practical experience with SQL databases.
Throughout his career, Bill has shared his knowledge to help other programmers achieve success and productivity. This book is full of good examples of bad practices including some that SEEM like they would help you out and ways that you can avoid them. I also enjoyed the comparison of the Active Record pattern versus the Repository pattern as it convinced me that the decision to use Repository on my current project was a reasonable one.
I am a strong advocate of best practices. I struggled for a long time with a database that had a large tree structure, so I’m a First, this is based on B6.