Home
SQL programmingYou can use the HCL OneDB™ implementation of the SQL language to develop applications for HCL OneDB™ database servers.
Guide to SQL: SyntaxThe HCL OneDB™ Guide to SQL: Syntax describes the syntax of the statements, data types, expressions, operators, and built-in functions of the HCL OneDB™ dialect of the SQL language.
SQL statementsThis chapter describes the syntax and semantics of SQL statements that are recognized by HCL OneDB™.
CREATE TEMP TABLE statementUse the CREATE TEMP TABLE statement to create a temporary table in the current database.
Column definition specification of the CREATE TEMP TABLE statementUse the Column Definition segment of the CREATE TEMP TABLE statement to declare the name and the data type (and optionally a default value and constraints) of a single column of the temporary table.

Column definition

Use the Column Definition segment of the CREATE TEMP TABLE statement to declare the name and the data type (and optionally a default value and constraints) of a single column of the temporary table.

Column Definition

Notes:

¹ See Data Type
² Use this path no more than once
³ See DEFAULT clause of CREATE TABLE
⁴ See Single-Column Constraint Format


Element	Description	Restrictions	Syntax
column	Name declared here for a column in the table	Must be unique in its table	Identifier

This portion of the CREATE TEMP TABLE statement resembles the corresponding syntax segment in the CREATE TABLE statement. The differences include these:

You cannot define a referential constraint on the column.
The data type cannot be IDSSECURITYLABEL.
The SECURED WITH label option is not supported for temporary tables.

Just as when you create permanent tables, any explicit or default storage size specification for a column of a built-in character type, such as CHAR, LVARCHAR, NCHAR, NVARCHAR, or VARCHAR, is interpreted in units of bytes, unless the SQL_LOGICAL_CHAR configuration parameter is set to enable logical character semantics for datatype declarations. See the HCL OneDB™ Administrator's Reference for more information about the effect of the SQL_LOGICAL_CHAR setting in locales that support multibyte code sets, such as UTF-8, where a single logical character can require more than one byte of storage.