News for hackers. Stuff that matters.
Re:Anatomy of a Crushing by rimantas on Tuesday March 08, 2011 @04:39PM (#2302696)

   I lived in constant fear of forgetting a WHERE clause.
For those in constant fear: http://dev.mysql.com/doc/refman/5.1/en/mysql-tips.html#safe-...
Re:Anatomy of a Crushing by idlewords on Tuesday March 08, 2011 @04:56PM (#2302739)
Ha, I half-remembered this existing and tried to Google my way to it, but to no avail. Thanks so much for the pointer!
Re:Anatomy of a Crushing by jtbigwoo on Tuesday March 08, 2011 @06:09PM (#2302985)
In a huge database, even a SELECT with no WHERE clause can tie up considerable resources.
Re:Anatomy of a Crushing by neilk on Tuesday March 08, 2011 @07:48PM (#2303284)
--i-am-a-dummy also limits the number of rows you can SELECT or JOIN.
Re:Anatomy of a Crushing by dasil003 on Tuesday March 08, 2011 @06:41PM (#2303087)
You can kill it though, use SHOW PROCESSLIST
Re:Anatomy of a Crushing by dools on Tuesday March 08, 2011 @07:50PM (#2303292)
I always write my WHERE clauses first whenever I do anything on a live dataset.
Re:Anatomy of a Crushing by SupremumLimit on Wednesday March 09, 2011 @12:21AM (#2303947)
I always had a rule to do everything inside a transaction. Having to commit a transaction gives you just enough pause to double check what you've done.
Re:Anatomy of a Crushing by shii on Tuesday March 08, 2011 @09:03PM (#2303474)
It's funny because I bookmarked this on pinboard.in