Let me tell you a story about breaking the login page. About 10 years ago, two of my colleagues at that time were supposed to delete around 10 test users from database, we had no clue about soft deletes (nor foreign keys for that matter) at that time so they decided to do a serious delete... I am sure you know where this is going. Both of them stared at the screen and confirmed multiple times that the delete clause is bullet proof, hit execute. And deleted 50k users from database!
Now here comes the fun part, the ONLY backup we had at that time was 3 days old on my laptop. So in the end they still partially saved the day and we lost 3 days worth of new users
Let me tell you a story about breaking the login page. About 10 years ago, two of my colleagues at that time were supposed to delete around 10 test users from database, we had no clue about soft deletes (nor foreign keys for that matter) at that time so they decided to do a serious delete... I am sure you know where this is going. Both of them stared at the screen and confirmed multiple times that the delete clause is bullet proof, hit execute. And deleted 50k users from database!
Now here comes the fun part, the ONLY backup we had at that time was 3 days old on my laptop. So in the end they still partially saved the day and we lost 3 days worth of new users
ahahahah two human beings being sure that the change is safe. That's definitely a sort of an "echo chamber" right there :D
And that's exact reason why you run select first with the same condition to see what will be deleted. 🤔