Neoview SQL Reference Manual (R2.4)

MAXVALUE is specified, maximum value is the maximum value of the data type of the
IDENTITY column.
MINVALUE signed-numeric-literal | NO MINVALUE
Positive value (not 0 (zero) or less than 0 (zero). If NO MINVALUE is specified, minimum
value is the minimum value of the data type of the IDENTITY column. If the data type
is LARGEINT, the minimum default value is zero, not -9223372036854775808.
NO CYCLE
means that when the MAXVALUE maximum is reached for the IDENTITY column, an
error is raised that says the maximum has been exceeded. Values will not be restarted.
If an artificially low cycle range was created by setting the MAXVALUE value lower than
the natural maximum allowed for the data type, you can use the ALTER TABLE ALTER
COLUMN SET MAXVALUE option to raise the maximum value, including up to the
natural maximum allowed for the data type. This allows more available values in the
cycle range for the internal sequence generator. Inserts will be successful until the new
maxvalue is reached. For more information, see the “ALTER TABLE Statement” (page 45).
CONSTRAINT constraint
specifies a name for the column or table constraint. constraint must have the same schema
as table and must be unique among constraint names in its schema. If you omit the schema
portions of the name you specify in constraint, Neoview SQL expands the constraint
name by using the schema for table. See “Database Object Names” (page 228).
NOT NULL
is a column constraint that specifies that the column cannot contain nulls. If you omit NOT
NULL, nulls are allowed in the column. If you specify both NOT NULL and NO DEFAULT,
each row inserted in the table must include a value for the column. See “Null” (page 265).
PRIMARY KEY [ASC[ENDING] | DESC[ENDING]] or PRIMARY KEY (key-column-list)
is a column that specifies a column or set of columns as the primary key for the table.
key-column-list cannot include more than one occurrence of the same column.
ASCENDING and DESCENDING specify the direction for entries in one column within the
key. The default is ASCENDING.
The PRIMARY KEY value in each row of the table must be unique within the table. A
PRIMARY KEY defined for a set of columns implies that the column values are unique and
not null. You can specify PRIMARY KEY only once on any CREATE TABLE statement.
Neoview SQL uses the primary key as the clustering key of the table in order to avoid creating
a separate, unique index to implement the primary key constraint.
If you do not specify a PRIMARY KEY constraint, Neoview SQL cannot implement the
primary key as the clustering key.
CHECK (condition)
is a constraint that specifies a condition that must be satisfied for each row in the table. See
“Search Condition” (page 286).
Neoview SQL checks the condition whenever an operation occurs that might affect its value.
The operation is allowed if the predicate in the condition evaluates to TRUE or null but
prohibited if the predicate evaluates to FALSE.
You cannot refer to the CURRENT_DATE, CURRENT_TIME, or CURRENT_TIMESTAMP
function in a CHECK constraint, and you cannot use subqueries in a CHECK constraint. For
information about the CHECK constraint and string literals, see the Neoview Character Sets
Administrator's Guide.
NOT CASESPECIFIC
is a column constraint that specifies that the column contains strings that are not case specific.
The default is CASESPECIFIC. Comparison between two values is done in a case insensitive
way only if both are case insensitive. This applies to comparison in a binary predicate, LIKE
CREATE TABLE Statement 75