this post was submitted on 11 Oct 2023
387 points (97.8% liked)

Programming

17313 readers
181 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

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 [email protected]



founded 1 year ago
MODERATORS
 

"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
[–] [email protected] 10 points 1 year ago (1 children)

I have done this too. Shit happens.

One of my co-workers used to write UPDATE statements backwards limit then where etc, to prevent this stuff, feels like a bit of a faff to me.

[–] [email protected] 26 points 1 year ago (2 children)

I always write it as a select, before turning it into a delete or update. I have burned myself too often already.

[–] DacoTaco 2 points 1 year ago

^ this is a very good tip that ive been using myself too

[–] drekly 2 points 1 year ago

Oh I did that like a year ago.

And then last night had an error that led me back near this code and stupidly thought "hey it'd look neater if those numbers were in order"