Programming

17511 readers

350 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

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

And a development environment. And not touch production without running the exact code at least once and being well slept.

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

Fuck that, get shit housed and still do it right. That's a pro.

[–] spartanatreyu@programming.dev 19 points 1 year ago (1 children)

That's not pro, that's just reckless gambling.

[–] snail_hatan@lemmy.ml 3 points 1 year ago

Totally right! You must set yourself up so a fool can run in prod and produce the expected result. Which is the purpose of a test env.

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

Replied hastily, but the way to run db statements in prod while dealing with sleep deprivation and drinking too much is to run it a bunch in several test env scenarios so you're just copy pasting to prod and it CAN confidently be done. Also enable transactions and determine several, valid smoke tests.

Edit: a -> several