NOTE:
table, the actual time is usually a few seconds longer than value.
RESET
removes the dynamic timeout value (if set) for the specified table, resetting the timeout value
to the static values set during explicit Neoview SQL compilations. The RESET option with
an asterisk resets the dynamic timeout value (lock or stream timeout, as specified) for all
tables. The RESET option for a specific table does not override a dynamic timeout value that
was set for all tables. See
Considerations for SET TABLE TIMEOUT
•
The SET TABLE TIMEOUT statement does not perform any security checks on a table.
•
A CONTROL statement is a directive that affects the compilation of subsequent DML
statements but produces no executable code. A SET TABLE TIMEOUT statement, however,
produces executable code and has no effect on the compilation of other statements.
•
The SET TABLE TIMEOUT statement does not change the Neoview SQL compilation defaults
or CONTROL statement settings. A DML statement explicitly compiled after the execution
of a SET TABLE TIMEOUT statement internally contains the static CONTROL statement
timeout values, which are overridden by SET TABLE TIMEOUT.
Examples of SET TABLE TIMEOUT
•
Set the lock timeout value for all the tables to 30 seconds for the current session:
SET TABLE * TIMEOUT 3000;
•
Set the lock timeout value for the CUSTOMER table to one minute:
SET TABLE customer TIMEOUT '6000';
SELECT custnum, custname FROM customer;
•
Reset the timeout value for the CUSTOMER table to 30 seconds (set earlier for all tables):
SET TABLE customer TIMEOUT RESET;
•
This statement has no effect; the PARTS table still uses the lock timeout value of 30 seconds
(set earlier for all tables):
SET TABLE parts TIMEOUT RESET;
•
Reset all the lock timeout settings. All tables will use the static lock timeout value specified
by the system or by the CONTROL statement:
SET TABLE * TIMEOUT RESET;
Because of overhead processing by Neoview SQL after a timeout occurs on a locked
"Examples of SET TABLE
TIMEOUT".
SET TABLE TIMEOUT Statement
187