Not sure what sizes of tables you deal with on a regular basis, but this would not be possible on very large tables. Imagine trying to cache a few million rows, detect someone using one of the MANY different types of destructive commands available across MANY different database providers and versions of each of those.
Again, this is what a DEV,QA,PROD environment is for. DEV, do what you want. QA, do what you want a bit more carefully, PROD, write up what you are going to do, have other eyes look at what you want to do, get consensus on it, then cringe as you do it. 