5 ms·
In most of my scenarios, I'd actually rather cause a catastrophic global change than a silent subtle corruption of a handful of rows
by menacingly 3y ago
In most of my scenarios, I'd actually rather cause a catastrophic global change than a silent subtle corruption of a handful of rows
- gumballindie 3y agoThat may be fun in a trivial setup such as op’s but when millions of customers or billions of transactions are affected it’s a nightmare. A competent engineer runs queries against a local and then a uat db, verifies results and then on prod. But if you must do it in prod then it must be limited in scope.
- menacingly 3y agoWe're on the same page with the best approach, I just don't consider corrupting an unpredictable subset of my database much of an improvement. It's not closer to correct, it's just still incorrect.