Table of Contents
Advertisement
NO INSERTLOG | INSERTLOG
specifies whether update and delete operations are recorded in the table's IUD log.
When a table is defined with the INSERTLOG attribute, logging operations ignore delete
and update operations and log inserts only.
ADD [COLUMN] column-definition
adds a column to table. This option is valid only for the ALTER TABLE statement.
The clauses for the column-definition are:
column-name
specifies the name for the new column in the table. column-name is an SQL identifier.
column-name must be unique among column names in the table. If the column name
is a Neoview SQL reserved word, you must delimit it by enclosing it in double quotes.
For example: "sql".myview. See
data-type
specifies is the data type of the values that can be stored in column. See
(page
ADD [CONSTRAINT constraint] table-constraint
adds a constraint to the table and optionally specifies constraint as the name for the
constraint. The new constraint must be consistent with any data already present in the table.
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
If you do not specify a constraint name, Neoview SQL constructs an SQL identifier as the
name for the constraint in the schema for table. The identifier consists of the fully qualified
table name concatenated with a system-generated unique identifier. For example, a
constraint on table A.B.C might be assigned a name such as A.B.C_123..._01... .
DROP CONSTRAINT constraint [RESTRICT | CASCADE]
drops a constraint from the table. The new constraint must be specified.
If you drop a constraint, Neoview SQL drops its dependent index if Neoview SQL originally
created the same index. If the constraint uses an existing index, the index is not dropped.
The default is RESTRICT.
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
If you do not specify a constraint name, Neoview SQL constructs an SQL identifier as the
name for the constraint in the schema for table. The identifier consists of the fully qualified
table name concatenated with a system-generated unique identifier. For example, a
constraint on table A.B.C might be assigned a name such as A.B.C_123..._01... .
RENAME new-name[CASCADE]
changes the logical name of the object within the same schema.
new-name
specifies the new name of the object after the RENAME operation occurs.
CASCADE
specifies that indexes and constraints on the renamed object will be renamed.
48
SQL Statements
197).
"Identifiers" (page
220).
"Database Object Names" (page
"Database Object Names" (page
"Data Types"
196).
196).
Advertisement
Table of Contents
