Double/triple check the messages/console for results. Look good?
Commit;
Worried?
Rollback;
Just be sure to mind your transaction logs for long running queries and by all things holy be sure you’re not doing this to a live db with a ton of transactions since you’re basically pausing any updates until the commit or rollback on the affected tables
Transactions are your friend here
Then
Double/triple check the messages/console for results. Look good?
Worried?
Just be sure to mind your transaction logs for long running queries and by all things holy be sure you’re not doing this to a live db with a ton of transactions since you’re basically pausing any updates until the commit or rollback on the affected tables
This makes it safer but like… don’t run queries on production outside emergencies ever.
That transaction frame, depending on your specific DB, may cause severe performance side effects.
Look, the safe approach is to write it into something, PR it, get it reviewed, and then run it as part of a structured deployment process.
Absolutely. It should have been tested and verified.
Me: “Ok. What’s the big deal.”
Also me: “Less than a million affected. That’s nothing.”
Still me: “Rule 1: Never let pesky details get in the way of a funny meme.”
Ultimately me: 😱😂 “That guy is in for a rough Monday!”