|
Option
|
Description
|
|
-b count
|
Enables benchmark mode, in which printing of results from queries is turned off. Only the number of rows fetched is printed after every count records are read. Use this to time the execution of large queries without waiting for the results to be printed. Example: -b 1000
|
|
-c cmdfile
|
Executes the commands in the cmdfile. The cmdfile can contain multiple commands. See Interactive SQL Commands for JDBCISQL for more information. Example: -c test.sql
|
|
-d driver
|
Gives the driver name. If this option is not specified, then JDBCISQL connects to com.ddtek.jdbc.openaccess.OpenAccessDriver. Example: -d com.mydomain.mysw.jdbc.openaccess.OpenAccessDriver
|
|
-e
|
Echoes the command being executed to the standard out. This option can be used when JDBCISQL is set up to run automated test scripts so that the output file contains the command being executed. Example: -e
|
|
-h
|
Display command line usage. Example: -h
|
|
-m count
|
Specifies the maximum rows to be displayed. The default value is 100. When set to 0, there is no limit on the number of rows. Example: -m 200
|
|
-n cmdfile
|
Executes the commands in the cmdfile. The cmdfile contains Unicode commands and must be in UTF-8 format. Example: -n utest.sql
|
|
-p prefix
|
Appends the prefix with connection properties supplied in the connect command to form the URL for the connection. If this option is not specified, then JDBCISQL uses jdbc:openaccess://. Example: -p jdbc:openaccess://localhost:19986;ServerDataSource=You can then use the following command to connect to a data source named example.ISQL> connect pooh*bear@example
|
|
-q |
Enables quiet mode. Output such as the start up message and time to complete the operation is not sent to the standard output.Example: -q
|
|
-u url |
Specifies the URL for the driver. This option is required when the –d option is used. When this option is used, connection properties given in connect command are ignored. Example: -u jdbc:myOA://localhost:19986;ServerDataSource=example;
|