The MySQL command line client has an argument "--i-am-a-dummy" that refuses to run UPDATE and DELETE's without a WHERE clause.
More commands could use options to adjust how big guns they let you fire at your feet with...
Such options might be more appealing to users if it were named something like "--extra-safety" or "--require-where".
Humorless users can use "--safe-updates"
http://dev.mysql.com/doc/refman/5.0/en/mysql-tips.html#safe-...
...which is not the default. Fuck them.
I always SELECT first and confirm I got the right result. Then I add the DELETE just before SELECT and commment out the SELECT line. Never fails!
After doing that on a local db a couple of times, I started just writing the where clause first. Goes like this
WHERE id = 1 ctrl + a DELETE FROM....
Found it's also helpful for writing SELECTS and avoiding the whole "oh crap, now let's load the entire DB" type of moments.
Re:Heroku Fucking Console
by schrodinger on Friday March 01, 2013 @01:33PM
(#5306017)
If you're in a GUI where you can run only the highlighted code, I do this:
select * -- delete
from sometable
where id = 1
Then you can run the whole thing to see what would be deleted, and highlight starting at the word delete to actually delete.
Re:Heroku Fucking Console
by methurston on Friday March 01, 2013 @02:57PM
(#5306587)
I do this too,
If I'm saving the file for reuse, I wrap the entire thing in /* */ when I'm done just in case I accidentally hit run script instead of run statement.
Re:Heroku Fucking Console
by TrunkleBob on Friday March 01, 2013 @03:31PM
(#5306772)
Do that once on a production system in the middle of a shipping run. Lesson learned.
All my deletes written first as selects now, as a sibling comment suggested.
Crap.. I meant "DELETE FROM some_table WHERE id=1"
sighs