Script Editor

Previous  Top  Next

The Script Editor works pretty much the same as the SQL Editor. It has the same construct for SQL Pages and its output goes to the Server Output window - Tools | Server Output.


Note: There is no Script Editor available on ADO or ODBC connections.


If an error occurs, it will show a dialog that allows you to ignore the error and continue or to abort the current script. If you don't want this dialog to show, edit the Script Preferences.


Script Editor Error Dialog


The Ignore all errors for this run checkbox allows you to ignore any errors for the current run. Once you use the Run (F9) button, this checkbox is reset.


Linking Scripts

The Script Editor in Database Workbench supports the INPUT directive. Syntax is:


INPUT 'path\filename.extension';


Database Workbench will load the filename identified by "filename.extension" and execute it 'inline'. After the loaded script has finished executing, it will continue executing the calling script. Loaded scripts will be shown on a seperate SQL Page.


If no path information is used, the current path will be used in the attempt to load the secondary script file.



The Script Editor uses the same transaction/autocommit setting as the SQL Editor - the other tab in this editor window. For more information about transactions, see SQL Editor