Client Side Scripting
Table of contents
Overview
You can use special commands in the SQL Editor.
These commands are executed on Team Edition's side, not on the server-side.
Supported commands
Team Edition supports the following commands:
Command | Database | Description |
---|---|---|
@ai message ![]() | All | Sends a natural-language message to the AI assistant. The AI processes the message and generates an appropriate SQL query or action based on your input. For more details, see AI command. |
@set var = value | All | Sets a script variable. You can use expressions as a value. Variables can be used as SQL queries input parameters. For more information, see Dynamic parameter bindings. |
@unset var | All | Unsets a script variable. |
@echo message | All | Prints message to output log. You can use a macro in a message (for example ${var} ). |
@include fileName | All | - Executes a specified file name, - Can be used in scripts, - Opens a new SQL console with the specified file and processes SQL queries as in a regular SQL editor. |
@export { ... } | All | Opens the data transfer wizard with predefined settings. For more information, see Export command. |
source fileName | MySQL | The same as @include but in MySQL CLI syntax. |
define var = value | Exasol | The same as @set but in Exasol EXAPlus syntax. |
Tip: You can use multiline commands by enclosing them in
@@
. For example:
@@set var = 'long multiline value' @@