this post was submitted on 11 Oct 2023
418 points (97.9% liked)

Programming

17309 readers
272 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
[–] MarekKnapek 4 points 1 year ago

Sh1t already happened, but on the bright side, you learn for the next time. Some tips:

  • Make clone of production environment into testing environment. Do stuff there, and after it is tested / verified, do the same in production. Emphasis on "do exactly the same".
  • Make regular automatic backup. From time to time, do a backup restore to another computer (VM) and verify that it is restored successfully and is actually usable.
  • Poor man's backup is automatic daily (hourly?) snapshots on BTRFS / ZFS / EXT4 filesystems or VolumeShadowCopy on NTFS filesystem.
  • Before any UPDATE do a SELECT and verify the data you are modifying are the data you actually want to modify.
  • Use a transactions in form of BEGIN TRANSACTION; UPDATE stuff; ROLLBACK; and observe the DB behavior, or see how many rows are affected.
  • Somebody has even moar tips, I'm sure. Please write them below.