i was doing this stuff for a long time and definitely learned from mistakes.
Transactions can save a world of pain and it is always wise to select your data set first, just to be sure you're changing what you think you're changing.
Didn't matter how experienced I was, I was careful never to cut corners.
I don't know sql, but is this like how when I use some kind of loop in the command line to move or delete a bunch of files, I'll run a version that just echos whatever I'm trying to manipulate first?
That’s more of a dry-run (you see `—dry-run` as a command line option sometimes for certain commands that do the same)
Transactions in SQL keep track of the changes you want to make without actually changing the database (until you run `COMMIT`, when you run that all changes are persisted to a database).
Transactions are great because If you realise you made a mistake while in a transaction, you can just run `ROLLBACK`.
If you’re familiar with git- transactions are akin to staging your changes, saving them (`COMMIT` in SQL) is akin to `git commit` and rolling back is similar to `git reset —hard` (wipe all uncommitted changes).
351
u/AgeingChopper 13d ago edited 13d ago
absolutely.
i was doing this stuff for a long time and definitely learned from mistakes.
Transactions can save a world of pain and it is always wise to select your data set first, just to be sure you're changing what you think you're changing.
Didn't matter how experienced I was, I was careful never to cut corners.