Sets the string that indicates the end of a statement in Interactive SQL.
In general, there is no need to change the command delimiter. You should leave it as a semicolon.
An alternative to using a semicolon or another string as a statement delimiter is to enter the separator go on a line by itself, at the beginning of the line. See Introduction to batches.
Specifying go on its own line at the beginning of the line is always recognized as a command delimiter, even if you set the command_delimiter option to a different value.
The command_delimiter value can be any string of characters with the following restrictions:
If the command delimiter is set to a string beginning with a character that is valid in identifiers, the command delimiter must be preceded by a space. The command delimiter is case sensitive. You must enclose the new command delimiter in single quotation marks. When the command delimiter is a semicolon (the default), no space is required before the semicolon.
The following example sets the command delimiter to a tilde:
SET OPTION command_delimiter='~'; MESSAGE 'hello'~
You can also use the Interactive SQL -d option to set the command delimiter without including a SET OPTION command_delimiter statement in a .sql file. For example, if you have a script file named test.sql that uses tildes (~) as the command delimiter, you could run:
dbisql -d "~" test.sql
|Send feedback about this page via email or DocCommentXchange||Copyright © 2008, iAnywhere Solutions, Inc. - SQL Anywhere 11.0.0|