You must log in or register to comment.
“I didn’t put a WHERE clause in that DELETE statement”
As a side note, DBeaver actually asks for confirmation if it thinks you are about to do something wonky. I think it’s quite telling just how common this mistake is. We’ve all been there
Update and delete should require a where clause. You can always use true or 1 = 1, the gain from omitting it is minimal.
The fact that no DBMS ever decided to implement this, not even as an option is quite distressing.
Embrace it as you are now officially a developer
At some point this is just a rite of passage
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.
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.
DB admins rawdogging the prod postgres on a Friday evening.
I don’t even work with databases but I still have a fear of possibly doing this someday.
If it happens, it’s a lack of control, and, at least mostly, not your fault
Don’t call it “accidental database deletion”. Call it “unannounced live exercise of backup procedure”.
Sometimes I dream of getting fired for accidentally doing shit like this. Sweet relief…
Good companies wouldn’t fire someone for this because:
-
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.
-
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.
-
