Use the Stop button to cancel an Interactive SQL Classic (dbisqlc) command. On UNIX, click Ctrl+C to cancel a command. Stop cancels current processing and prompts for the next command.
When you cancel a command, one of three different errors is reported, depending upon when the end is detected.
If the cancellation is detected when Interactive SQL Classic is processing the request (as opposed to the database engine), you see:
dbisql command terminated by user
Interactive SQL Classic stops processing immediately and the database transaction is left alone.
If the cancellation is detected while the database engine is processing a data definition command (CREATE, DROP, ALTER, and so on,) you see:
Terminated by user -- transaction rolled back
Since data definition commands all perform a COMMIT automatically before the command starts, the effect of the ROLLBACK is to just cancel the current command.
This message also occurs when the database engine is running in bulk operations mode executing a command that modifies the database (INSERT and DELETE). In this case, ROLLBACK cancels not only the current command, but everything that has been done since the last COMMIT or ROLLBACK. In some cases, it may take a considerable amount of time for the database engine to perform the automatic ROLLBACK.
If the cancel is detected by the database engine while processing a standard data manipulation command (SELECT, INSERT, DELETE, and so on,) and the engine is not running in bulk operations mode, you see.
Statement interrupted by user.
The effects of the current command are undone, but the rest of the transaction is left intact.
