4 ms·
> Instead of providing the IDs of the intended app being marked for deactivation, the team provided the IDs of the entire cloud site where the apps were to be d
by kingcharles 5y ago
> Instead of providing the IDs of the intended app being marked for deactivation, the team provided the IDs of the entire cloud site where the apps were to be deactivated.
This reminds me of the time I was tasked with changing the gender of a user to female on the production database (since the feature was not available through an interface at the time) and so I opened SQL Explorer on our live database and ran a quick update. Except I forgot the UserID param and accidentally changed over a million registered users to female.
A colleague came up with the idea to use the person's title as a hint to repopulate the database, which worked for Mr, Mrs and Ms.
I apologise now to all the doctors that found they had undergone nonconsensual gender reassignment.
- wdb 5y agoIf one record needs to be changed, I typically, just manually do it via the UI :)
- petepete 5y agoAll databases should offer an --i-am-a-dummy mode, and probably enable it by default in clients. It prevents you from running update or delete statements that don't have a where clause. https://dev.mysql.com/doc/refman/8.0/en/mysql-tips.html#safe-updates https://dev.mysql.com/doc/refman/8.0/en/mysql-tips.html#safe...
- chrisandchris 5y agoThat's why some databases have a "where condition required on update" so you won't hit that wall (assuming there were no other where conditions involved).