this post was submitted on 11 Oct 2023
0 points (NaN% liked)

Programming

17008 readers
346 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 !webdev@programming.dev



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
[–] AlphaOmega@lemmy.world 0 points 11 months ago* (last edited 11 months ago) (1 children)

This is a hard lesson to learn. From now on, my guess is you will have dozens of backups.

[–] ReluctantMuskrat@lemmy.world 0 points 11 months ago (1 children)

And always use a transaction so you're required to commit to make it permanent. See an unexpected result? Rollback.

[–] sim642@lemm.ee 0 points 11 months ago (1 children)

Transactions aren't backups. You can just as easily commit before fully realizing it. Backups, backups, backups.

[–] elvith@feddit.de 0 points 11 months ago

Yes, but

  1. Begin transaction
  2. Update table set x='oopsie'
  3. Sees 42096 rows affected
  4. Rollback

Can prevent a restore, whereas doing the update with auto commit guarantees a restore on (mostly) every error you make