4 ms·
Hell - this could have been avoided if they weren't using graphical tools or had a database that used transactions.
by juan_juarez 14y ago
Hell - this could have been avoided if they weren't using graphical tools or had a database that used transactions.
- krallja 14y agoNeither of those things would have fixed this problem. 1. "Oops, I wrote TRUNCATE TABLE User instead of TRUNCATE TABLE Raids" 2. Transaction complete. ... ... "oops!"
- whatshisface 14y agoWell, to be fair it's harder to type User than it is to miss your rightclick by something that could have only been a few pixels.
- derekp7 14y agoAlso, I can't tell you how many times I've attempted to click on a button on a web form, and it was still loading and the button moved (along with a different button appearing in its place).
- themonk 14y agoWhy type "TRUNCATE TABLE Raids" every time? Type it once, test it, save as script, schedule that script.
- krallja 14y agoThat is definitely another bug in this company's process. This should have been automated. It's much harder to screw up running a script!
- ptaipale 14y agoNot really. You obviously haven't (yet) done anything like update t1 set status=0; where status=4; when you wanted to release (set status to 0) objects that are stuck in state 4, and let all other objects keep their existing statuses. This is an easy mistake to make on command line. I hate GUIs too but not having one doesn't really help when your fundamental operating model is wrong.
- devicenull 14y agoAnd that's why you use --i-am-a-dummy on the command line :) http://dev.mysql.com/doc/refman/4.1/en/mysql-command-options.html#option_mysql_safe-updates http://dev.mysql.com/doc/refman/4.1/en/mysql-command-options...