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

Programming

17373 readers
230 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] 52 points 1 year ago* (last edited 1 year ago) (2 children)

Postgres has a useful extension, pg_safeupdate

https://github.com/eradman/pg-safeupdate

It helps reduce these possibilities by requiring a where clause for updates or deletes.
I guess if you get into a habit of adding where 1=1 to the end of your SQL, it kind of defeats the purpose.

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

MySQL (and by extension, MariaDB) has an even better option:

mysql --i-am-a-dummy

[–] [email protected] 5 points 1 year ago

Amazing! These are going in my.conf ASAP.

[–] [email protected] 5 points 1 year ago

Transactions help more, IMO. The 1=1 becomes a real habit.