Bah!
I recently pulled an Old Man Idiocy when using TOAD (an excellent tool, but like all tools very dangerous in the hands of the unknowlegeable, forgetful or just plain lazy - last one applies in this case).
Asked to move an Oracle package from a test database schema into our production schema I proceeded to pull up the package in TOAD, did a create script to the clipboard, pasted it into the editor window in the target database session, edited the code to change the schema name and ran said code in the production database that night as requested.
Next day no-one could access the package code. It seems some witless dolt had removed all the permission grants and synonyms from the package.
Turns out I had neglected to double check the check-boxes on tab in the create script pop-up that controls the generated code closely enough, and had neglected to notice that the generated code contained the dreaded "drop object" syntax.
Not only that, I had neglected to recognize that that had happened when I did the code edit for schema name change. I mean, it was only hiding in plain sight on bloody line one.
Unfortunately, I rather like all the people I work with now, so I was forced to do the Bonehead Dance and wear the Pointy Hat of Not Being Smart instead of shifting blame to the intern or new hire as per industry standard practice.
D'oh!
Biting the hand that feeds IT
