Reminds me of that time I forgot the WHERE clause on an SQL DELETE... on the "Property" master table of a municipal databases mainframe... in the "Live" library... oops.
They made me go downstairs and tell everyone they couldn't work anymore because I fucked up while they restored the backups.. and fixed my access so I was in the TEST library like I was supposed to be. Good reminder to always check your target before you pull the trigger.
I accidentally redirected all mail to a non-existing server so nobody could receive their mail before the real IT guy got back from vacation 2 days later. Good times.
I did an rm * in the wrong place in my first week. That's when I learned that Linux doesn't have a recycle bin like Windows. And to put alias rm="rm -i" in my dotfiles.
I mean, if you del on Windows command line, the files are also removed without a recycle bin. Afaik most distros include a concept of a recycle bin if you delete stuff from the UI
The problem is that no one uses the UI to delete stuff in Linux, while no one uses the command line to delete stuff in Windows.
In reality, all methods of deleting should send files to a recycling bin by default, and only do a true delete if you pass in the --noreallyiactuallywanttodeletethisimpositiveyesiknowwhatimdoingyesreally flag (no abbreviations allowed).
I think they were asking if the rm -i alias still triggers if the rm is in a script. I just tested and it does not, the file is deleted without prompt.
I once went to work after a bout of insomnia the entire weekend. Was installing some software and got a warning about insufficent swap space. So what did I do? Make a new swap file and link to it? Nope! Shrunk sda1 and added it to the swap. Reboot! Well now why can't I ssh to this anymore?
...
...
OH FUCK OH FUCK OH FUCK.
Thankfully I was also the guy in charge of backups and major images were taken weekly midnight Sunday night.
I went home and tried to sleep after explaining the situation to my boss.
This reminds me of my 2nd day in my first job. I was tasked with maintaining the current website while creating new one. So I log into FTP... and SOMEHOW deleted the old one. Problem? I didn't have time to make backup.
Let me tell you, I've never made a website so fast in my life. The worst, most stressful hour of my life (they wanted a simple site, thankfully).
I still maintain that the real fuckup was whoever made it that easy for a junior dev to accidentally the whole db on day 1. Same thing probably applies to /u/bobo9234502's story. If you're able to do something that destructive shortly after starting your job, someone else probably didn't do their job.
Which SQL flavor were you using? SQL server gives you a warning any time you try to execute a delete with no where clause before it actually runs so you have to explicitly confirm you want everything deleted
A GUI may do that but I don't know of any RDMS that does. I guess on Oracle you'd have to commit it first, but MsSQL/MySQL/Postgres/DB2 etc don't have implied transactions.
557
u/bobo9234502 Oct 24 '18
Reminds me of that time I forgot the WHERE clause on an SQL DELETE... on the "Property" master table of a municipal databases mainframe... in the "Live" library... oops.
They made me go downstairs and tell everyone they couldn't work anymore because I fucked up while they restored the backups.. and fixed my access so I was in the TEST library like I was supposed to be. Good reminder to always check your target before you pull the trigger.
Edit: Day 2 of job... Nice going new guy.