SQL/MX 3.2.1 Reference Manual (H06.26+, J06.15+)

SQL/MX Statements
HP NonStop SQL/MX Release 3.2.1 Reference Manual—691117-005
2-30
Syntax Description of ALTER TABLE
Publish/Subscribe's embedded update and embedded delete statements are not
allowed on tables with referential integrity constraints.
You cannot create self-referencing foreign key constraints. When a foreign key
constraint is added to an existing table, NonStop SQL/MX verifies that the data
does not violate the constraint. If it does, a message is returned indicating the
constraint was not created.
RENAME TO new-table-object-name [CASCADE]
changes the logical name of the table within the schema.
new-table-object-name
specifies the new ANSI name of the table. The new ANSI name of the table
cannot be qualified. However, the renamed table will remain in the current
catalog and schema.
CASCADE
specifies that the system generated ANSI names of indexes and constraints
associated with the table will be renamed automatically.
Note. The CASCADE option renames the system-generated constraints and indexes
associated with the table. System-generated names have the following form:
<ANSI name prefix>_nnnnnnnnn_nnnn
where, n is a digit.
CASCADE option matches the ANSI name prefix of constraints with the table name.
The CASCADE option does not rename the constraints whose ANSI name prefix
does not match the table name. However, CASCADE option renames the system
generated index, irrespective of the name. Intermittent use of CASCADE option in
rename operations might lead to unintended results. Therefore, HP recommends that
you either use CASCADE continuously or do not use this option.
Note.
•
Renaming a table changes the text of referencing views, RI constraints, and triggers to
reference the new name.
•
RENAME TO changes the redefinition timestamp of the following objects:
°
The affected table.
°
All indexes on the table.
°
All the tables referenced by the affected table.
°
All the tables referencing the affected table.