Only in DbVisualizer Pro
This feature is only available in the DbVisualizer Pro edition.
A client-side command is a DbVisualizer specific command prefixed with the at-sign (@). These commands are used in SQL scripts executed either in the SQL Commander in the DbVisualizer UI or in the command-line interface, dbviscmd. Client-side commands are used to control the execution of scripts and run for example export and import functionality without needing to interact with the DbVisualizer UI. The @mail command sends emails with attachment support, useful when using @export and then to mail the result of a query.
You can use these DbVisualizer client-side commands in your SQL scripts. (These commands are processed by DbVisualizer and never sent to the database as-is).
|Use these command to execute an external script.|
Use this command to ignore any subsequent client side commands (except for the @command of course). Example
Use this command to export the result of a query.
Use this command to send emails and attach files.
|Import table data from CSV, Excel, and TEXT (fixed width column) files|
|Use this command to open the specified file in the associated tool. (Not supported in the command-line interface, dbviscmd).|
|Use this command to temporarily change the statement delimiter for a complex statement.|
|Use this command to execute a function or procedure.|
|Use this command to emit a beep sound, e.g. to indicate a significant point in a script.|
|Use this command to halt processing the specified number of milliseconds.|
|Use this command to write to the Log tab.|
|Use these commands to lower (iconify) or raise (restore) the DbVisualizer main window.|
|Use this command to show column information for a table. The table name may be qualified with a schema and/or database name.|
|Use this command to get the DDL for a database object.|
Use this command to write log messages to a named file. Examples
|This command is no longer supported anymore. Please use the @log command instead.|
|Use these commands to control what to do when a statement results in a warning or an error.|
Use these commands to control the Auto Commit state.
Offers a way to execute a script or part of a script without actually executing the command fully. As an example below no actual sleep will be done nor will the Select be executed.
The command is primarily used to debug scripts and check that script can actually be run. An exception to this is when used in connection with client-side import commands.
|Use these commands to explicitly commit or rollback updates.|
|Use these commands to enable or disable output to the DBMS Output tab for Oracle databases.|
|Use these commands to adjust the Max Rows and Max Chars limits for specific queries.|
Use this command to name any following result set. When the SQL statement is executed, the tab showing the result set is named using the supplied <name> parameter.
DbVisualizer will for the example above show the result of the select in a tab named MyActors
|@stop now||Stop the execution of the script.|