298
top 17 comments
sorted by: hot top controversial new old
[-] vanZuider@feddit.de 50 points 1 year ago

Don't call it "accidental database deletion". Call it "unannounced live exercise of backup procedure".

[-] saluki@discuss.tchncs.de 3 points 1 year ago

Either that or rapid exodus from the country

[-] Dasnap@lemmy.world 16 points 1 year ago

DB admins rawdogging the prod postgres on a Friday evening.

[-] jeena@jemmy.jeena.net 13 points 1 year ago

I did something like that once, I wasn't very good at SQL but I needed some data, so I logged in into the production database and run my SELECT queries, I didn't change anything so everything was good, or so I thought.

I created a cross product over tables with millions of entries and when it didn't respond I thought it was odd but it was time to go home anyway. On the way home they called me and asked what I did. They had to restart the DB server because once the cache timed out one application after another started failing.

[-] azimir@lemmy.ml 10 points 1 year ago

Ouch. Gotta wrap those deletes in a transaction and look before it rolls forward. Lessons learned. Time to see if the backups actually have any data on them.

[-] Lemming@lemmy.world 8 points 1 year ago

Embrace it as you are now officially a developer

[-] MajinBlayze@lemmy.world 2 points 1 year ago

At some point this is just a rite of passage

[-] azimir@lemmy.ml 4 points 1 year ago

Mine was to format the wrong computer on the first day of my first IT internship. I spent the next six weeks there fixing that oopsie.

[-] nigh7y@lemmy.ml 6 points 1 year ago* (last edited 1 year ago)

Sometimes I dream of getting fired for accidentally doing shit like this. Sweet relief...

[-] Dasnap@lemmy.world 6 points 1 year ago

Good companies wouldn't fire someone for this because:

  1. There should be processes in place to prevent this, or recover from this, anyway. It's a team/department failure and you would just be the straw that broke the camel's back.

  2. They now know you've experienced this and will hopefully know to never do it again. Bringing in someone else could just reintroduce the issue.

[-] Atarian@vlemmy.net 2 points 1 year ago

You just triggered my PTSD

[-] jtk@lemmy.sdf.org 1 points 1 year ago

I did quite a few bad things like that early on. Now I never type UPDATE or DELETE without first doing a SELECT and WHERE. It's easy to convert to a DELETE and UPDATEs tend to effect only a few fields at a time so the extra effort is worth the peace of mind. It's a good habit to form, I can't even think of the last time I did anything horrible.

this post was submitted on 25 Jun 2023
298 points (100.0% liked)

Programmer Humor

32058 readers
1312 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS