31–40 of 130 posts
Back in the 90s I remember a work colleague asking 'can you rollback a drop table?', to which I replied 'no', and all the blood drained from his face in seconds. It's one of those things you've heard happens to people, but until you see it, you can't quite believe it.
>_The first thing I did after the recovery marathon was to alias rm so that it instead works by moving stuff to /tmp
Always do a select with your criteria before doing a Delete or update. Don’t ask me how I learned this.
Once I wanted to do `rm -fr *~` to delete backup files, but the `~` key didn't register... Now I have learnt to instinctively stop before doing anything destructive and double-check and double-check again! This also applies to SQL `DELETE` and `UPDATE`! I know that `-r` was not neccessary but hey that was a biiiig mistake of mine!
I've just started my career - I wonder what my first fuck-up will be :)
/s
I wish a DELETE or UPDATE only affected a single row by default (and perhaps even wouldn't commit if it would hit multiple rows), unless a keyword for MANY or something similar was added. Aka DELETE ALL where x == y or DELETE MANY where x == y or perhaps you need an explicit limit for it to not be 1, so DELETE where x == y LIMIT ALL
Always do a select with your criteria before doing a Delete or update. Don’t ask me how I learned this.
>Don’t ask me how I learned this. Joke's on you, we all learned it this exact way.
thankfully my boss at the time was a amazing db admin and he helped me fixing my mistake.
Back in the 90s I remember a work colleague asking 'can you rollback a drop table?', to which I replied 'no', and all the blood drained from his face in seconds. It's one of those things you've heard happens to people, but until you see it, you can't quite believe it.
> can you rollback a drop table >_ The first thing I did after the recovery marathon was to alias rm so that it instead works by moving stuff to /tmp
fdisk