The following sample script file, called myScripts.txt, contains the following queries:
INSERT INTO EMPLOYEE VALUES(1, 'John Smith'); SELECT * FROM DEPARTMENT; GRANT DELETE ON EMPLOYEE TO USER1; LIST PERMISSIONS; UPDATE EMPLOYEE SET ID=2 WHERE ID=1;
If you set the verbose option for the myScripts.txt file, you receive output similar to the following:
Executing statement #1: INSERT INTO EMPLOYEE VALUES(1, 'John Smith')
1 row(s) affected
##:##:##.### [main] WARN c.u.mcpsql.sql.util.StatementUtil - skipping
statement #2: SELECT * FROM DEPARTMENT, only
commands that do not return result sets can be
ran via script mode.
skipping statement #2: SELECT * FROM DEPARTMENT, only commands that do not
return result sets can be ran via script mode.
Executing statement #3: GRANT DELETE ON EMPLOYEE TO USER1
1 row(s) affected
##:##:##.### [main] WARN c.u.mcpsql.sql.util.StatementUtil - skipping
statement #4: LIST PERMISSIONS, only commands
that do not return result sets can be ran via
script mode.
skipping statement #4: LIST PERMISSIONS, only commands that do not
return result sets can be ran via script mode.
Executing statement #5: UPDATE EMPLOYEE SET ID=2 WHERE ID=1
1 row(s) affected
| Note: | Warnings are returned for SELECT statements and LIST PERMISSIONS commands. |

