Building a Project is Dangerous

[ghyland]

I need to warn you about a very dangerous feature in your PLSQL Developer product.

I tried to run a build into our production database this morning using the project build utility and found that the build scripts kept executing after an error occured in the very first command file. This resulted in corruption to our production database and we are now having to roll forward recover to a point in time.

The project was set to Halt After First Error.

As I said the first file in the build sequence was a command file whose first line was WHENEVER SQLERROR EXIT ROLLBACK;

An error occurred in an autonomous PL/SQL block early on in the command file that halted execution of the command file itself. The problem then was that rest of the project items just kept on running/compiling.

 

[Marco Kalter]

This would imply that we need to support the WHENEVER ... EXIT SUCCESS|FAILURE syntax. If you specify FAILURE, the project would need to stop. I have added this to the list of enhancement requests.

 

[Marco Kalter]

You can download a pre-release that addresses this issue. The Command Window now supports the WHENEVER SQLERROR EXIT SUCCESS|FAILURE syntax. If you use the following command:

WHENEVER SQLERROR EXIT FAILURE

the script execution will stop whenever an SQL error occurs, and the project build will stop because you specified FAILURE. The default is SUCCESS, just like in SQL*Plus.