Check Your Subroutines - We are delivering our latest release to internal test today. Had a code review yesterday. Many issues were found. We are fixing the highest priority probl...
Now I guess a verification script might add a small amount of value. If somebody runs the script, we could determine whether the original script ran to completion. However now our team needs to spend some extra time to write a verification script. Here is the fault in the logic behind this idea. If somebody was going to make some mistakes with a SQL script, what makes you think they could write a verification script to detect the mistakes?
Personally I do not care much. I love writing scripts. The more the merrier. I just need to be given time to do so. Therefore I am not really going to complain about this new requirement. I might even write a few verification scripts that just DBMS_OUTPUT.PUT_LINE('Script verified!') and see if anybody cares. LOL. The downfall is once somebody detects the shennanigans, we are going to be required to write verifications scripts on the verification scripts.