Mass database deletes - always wait for the second request Mar01 '07
Sometimes people tell me to make mass deletes in certain database tables, and with a click of a button, I can wipe out thousands of rows of data.
In the business world, it's probably not good if someone didn't think through this type of request before asking me.
This is why I always make database backups immediately before I do any mass deletes.
Another thing I do is wait for the person to ask twice. While this may seem silly and redundant to some people, it's absolutely necessary when doing mass deletes.
The reason I do this is because when a person asks for something once, they may not really mean it. But if they ask twice, you know they're absolutely serious.
It's the exact kind of verification I need before proceeding.
Anybody can throw an idea out there, but how many can actually back the idea, when the time comes? It's a totally different playing field.
Categories: Data 
, Philosophy
Add Feedback (view all)
Leave feedback
is published and produced by Matt Thommes - an independent publishing enthusiast, mobile blogger, content creator, informative writer, web developer from Chicago.
Never one to conform, Matt intends to promote the effect the web has on our lives, in an effort to intensify, instruct, and clarify all that is happening around us.
- Griffin iMic for single-track recording
- Dreamhost enhanced web panel appearance
- Social networking: say it; don't spray it
Similar Entries
- Amazon SimpleDB: scalable database system (112 recent visits)
- Avoid direct database updates (3 recent visits)
- Organizing images with a database (3 recent visits)
- iTunes database file (1880 recent visits)
- Purchase 24 on iTunes, or wait until December? (2 recent visits)
- Just wait a little bit (1 recent visits)
Stats
2 unique visits since December 2008