Programming

17484 readers

236 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

364

I accidentally removed the WHERE clause from my SQL query in a personal tool. Every row is now the same. I overwrote 206,000+ rows. I have no backup, I am stupid. (lemmy.world)

submitted 1 year ago* (last edited 1 year ago) by drekly@lemmy.world to c/programming@programming.dev

113 comments fedilink hide all child comments

"UPDATE table_name SET w = $1, x = $2, z = $4 WHERE y = $3 RETURNING *",

does not do the same as

"UPDATE table_name SET w = $1, x = $2, y = $3, z = $4 RETURNING *",

It's 2 am and my mind blanked out the WHERE, and just wanted the numbers neatly in order of 1234.

idiot.

FML.

you are viewing a single comment's thread
view the rest of the comments

[–] MonkCanatella@sh.itjust.works 36 points 1 year ago* (last edited 1 year ago) (4 children)

this folks, is why you don't raw dog sql like some caveman

[–] drekly@lemmy.world 13 points 1 year ago

Me only know caveman. Not have big brain only smooth brain

[–] XTornado@lemmy.ml 2 points 1 year ago (1 children)

But the adrenaline man... some of us are jonkies of adrenaline but we are too afraid of anything more of physically dangerous...

[–] MonkCanatella@sh.itjust.works 2 points 1 year ago

You may be interested in suicide linux then. it's a distro that wipes your entire hard drive if you mistype a command

[–] groucho@lemmy.sdf.org 2 points 1 year ago (3 children)

Yep. If you're in a situation where you have to write SQL on the fly in prod, you have already failed.

[–] XTornado@lemmy.ml 4 points 1 year ago* (last edited 1 year ago)

Me doing it for multiple years in a Bank....Uhm...

(let's just say I am not outting my money near them... and not just because of that but other things...)

[–] MonkCanatella@sh.itjust.works 3 points 1 year ago

it's time to commit sqlpukku

[–] Malfeasant@lemm.ee 3 points 1 year ago (1 children)

Tell that to my former employer...

[–] groucho@lemmy.sdf.org 1 points 1 year ago

Yeah, I swear it's part of the culture at some places. At my first full-time job, my boss dropped the production database the week before I started. They lost at least a day of records because of it and he spent most of the first day telling me why writing sql in prod was bad.

[–] olafurp@lemmy.world 1 points 1 year ago (1 children)

Raw dog is the fastest way to finish a task.

productivity
risk

It's a trade-off

[–] Sharpiemarker@feddit.de 1 points 1 year ago (1 children)

There's no way you're endorsing the way OP handled their data right?

[–] olafurp@lemmy.world 4 points 1 year ago* (last edited 1 year ago) (1 children)

No, but people are sometimes forced to do these things because of pressure from management and/or lack of infrastructure to do it in any other way.

Definitely don't endorse it but I have done it. Think of a "Everything is down" situation that can be fixed in 1 minute with SQL.

[–] Sharpiemarker@feddit.de 1 points 1 year ago

Got it. I'm with you.