this post was submitted on 11 Oct 2023
362 points (97.6% liked)

Programming

17001 readers
330 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] 33 points 11 months ago (3 children)

Always SELECT first. No exceptions.

[–] [email protected] 12 points 11 months ago* (last edited 11 months ago)

Better yet... Always use a transaction when trying new SQL/doing manual steps and have backups.

[–] [email protected] 4 points 11 months ago (1 children)
[–] [email protected] 16 points 11 months ago

By running a select query first, you get a nice list of the rows you are going to change. If the list is the entire set, you'll likely notice.

If it looks good, you run the update query using the same where clause.

But that's for manual changes. OP's update statement looks like it might be generated from code, in which case this wouldn't have helped.

[–] [email protected] 3 points 11 months ago

I did when I made the query a year ago. Dumdum sleep deprived brain thought it would look more organised this way