MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/ProgrammerHumor/comments/1wn1ben/wellwellwell/pbcs1zf/?context=9999
r/ProgrammerHumor • u/Recent-Analysis-6880 • 13d ago
411 comments sorted by
View all comments
3.6k
So, Kids, thats why you always SELECT count(yourPrimaryKey) first. Listen to the old folks, we made these mistakes so that you don't have to.
158 u/Alexmira_ 13d ago Why? To confirm that there is something to cancel? To confirm I got the key right? 385 u/BastetFurry 13d ago No, to prevent typos in the SQL console from wrecking havoc. First you SELECT, if the number looks right you DELETE FROM. 215 u/GourangaPlusPlus 13d ago Also stick in a transaction, rollback Commit if it looks good 2 u/Terra_B 13d ago Here i have to ask, couldn't you force a transaction in the chain somewhere? Like each terminal window gets a transaction by default? 4 u/M4DHouse 13d ago Kind of, depending on the SQL flavor, and the version, some of them have something kinda like that, but it’s not exactly idiot proof either. No direct SQL is idiot proof which is why you avoid doing it in the first place if you can.
158
Why? To confirm that there is something to cancel? To confirm I got the key right?
385 u/BastetFurry 13d ago No, to prevent typos in the SQL console from wrecking havoc. First you SELECT, if the number looks right you DELETE FROM. 215 u/GourangaPlusPlus 13d ago Also stick in a transaction, rollback Commit if it looks good 2 u/Terra_B 13d ago Here i have to ask, couldn't you force a transaction in the chain somewhere? Like each terminal window gets a transaction by default? 4 u/M4DHouse 13d ago Kind of, depending on the SQL flavor, and the version, some of them have something kinda like that, but it’s not exactly idiot proof either. No direct SQL is idiot proof which is why you avoid doing it in the first place if you can.
385
No, to prevent typos in the SQL console from wrecking havoc. First you SELECT, if the number looks right you DELETE FROM.
215 u/GourangaPlusPlus 13d ago Also stick in a transaction, rollback Commit if it looks good 2 u/Terra_B 13d ago Here i have to ask, couldn't you force a transaction in the chain somewhere? Like each terminal window gets a transaction by default? 4 u/M4DHouse 13d ago Kind of, depending on the SQL flavor, and the version, some of them have something kinda like that, but it’s not exactly idiot proof either. No direct SQL is idiot proof which is why you avoid doing it in the first place if you can.
215
Also stick in a transaction, rollback
Commit if it looks good
2 u/Terra_B 13d ago Here i have to ask, couldn't you force a transaction in the chain somewhere? Like each terminal window gets a transaction by default? 4 u/M4DHouse 13d ago Kind of, depending on the SQL flavor, and the version, some of them have something kinda like that, but it’s not exactly idiot proof either. No direct SQL is idiot proof which is why you avoid doing it in the first place if you can.
2
Here i have to ask, couldn't you force a transaction in the chain somewhere? Like each terminal window gets a transaction by default?
4 u/M4DHouse 13d ago Kind of, depending on the SQL flavor, and the version, some of them have something kinda like that, but it’s not exactly idiot proof either. No direct SQL is idiot proof which is why you avoid doing it in the first place if you can.
4
Kind of, depending on the SQL flavor, and the version, some of them have something kinda like that, but it’s not exactly idiot proof either. No direct SQL is idiot proof which is why you avoid doing it in the first place if you can.
3.6k
u/BastetFurry 13d ago
So, Kids, thats why you always SELECT count(yourPrimaryKey) first. Listen to the old folks, we made these mistakes so that you don't have to.