364
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 11 Oct 2023
364 points (97.6% liked)
Programming
17314 readers
141 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 2 years ago
MODERATORS
Always SELECT first. No exceptions.
Better yet... Always use a transaction when trying new SQL/doing manual steps and have backups.
mind explaining?
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.
I did when I made the query a year ago. Dumdum sleep deprived brain thought it would look more organised this way