1.0

Table Of Contents
Species the action taken on the global temporary table when a rollback operation is performed. On a ROLLBACK
of the transaction, if the table was created within it, the table will be dropped. If the table was dropped in the
transaction, the table will not be restored without the data.
ON ROLLBACK DELETE ROWS
This is the default value for NOT LOGGED. NOT LOGGED [ON ROLLBACK DELETE ROWS ]] species
the action that is to be taken on the global temporary table when a ROLLBACK operation is performed. If the
table data has been changed, all the rows will be deleted.
Restrictions on declared Global Temporary Tables
Temporary tables can be declared only in the SESSION schema. You should never declare a physical schema
with the SESSION name.
SQLFire does not support certain actions on temporary tables. Some of these features are specic to temporary
tables and some are specic to SQLFire.
Temporary tables cannot be specied in the following statements:
ALTER TABLE
CREATE INDEX
CREATE SYNONYM
CREATE TRIGGER
CREATE VIEW
GRANT
LOCK TABLE
RENAME
REVOKE
The following features cannot be used with temporary tables:
Synonyms, triggers and views on SESSION schema tables (including physical tables and temporary tables)
Caching statements that reference SESSION schema tables and views
Temporary tables cannot be specied in referential constraints and primary keys
Temporary tables cannot be referenced in a triggered-SQL-statement
Check constraints on columns
Generated-column-spec
Importing into temporary tables
If a statement that performs an insert, update, or delete to the temporary table encounters an error, all the rows
of the temporary table are deleted.
The following data types cannot be used with Declared Global Temporary Tables:
BLOB
CHAR FOR BIT DATA
CLOB
LONG VARCHAR
LONG VARCHAR FOR BIT DATA
VARCHAR FOR BIT DATA
XML
The following is a list of DB2 UDB DECLARE GLOBAL TEMPORARY TABLE functions that are not
supported by SQLFire:
IDENTITY column-options
471
SQL Language Reference