>
>Please don't take these suggestions as sarcasm. Relying on your tools to catch
>anything other than syntax errors is a bad idea. It builds in a false sense of
>security.
I couldn't possibly disagree that Q/A is a good idea, but so is
defense in depth. That's why we train drivers AND install
Hi,
I have two alternative suggestions.
1. Test your code. Simple test cases will ferret out these problems before they hit a
production environment.
2. Peer review. Let someone else look at your code before you migrate it to a
production environment. This, in my experience, is an effective wa
welcome to the joys of being a DBA ... :)
That's why restorable backups, tst and dev environments are so so important.
And yes, this kind of thing has kept me (and many others) busy more than once
after a too speedily executed SQL statement.
regards
Rob
-Original Message-
From: Dave Dyer
