SQL/MX 3.1 Reference Manual (H06.23+, J06.12+)

SQL/MX Statements
HP NonStop SQL/MX Release 3.1 Reference Manual—663850-001
2-33
Considerations for ALTER TABLE
•
The user-specified recalibration value must not be greater than MAXVALUE option
of the internal sequence generator.
•
The default specification type must be GENERATED BY DEFAULT AS IDENTITY.
ERROR[1601] is raised for default specification type GENERATED ALWAYS AS
IDENTITY.
•
The user-specified recalibration value must not be less than the START WITH and
MINVALUE options of the internal sequence generator.
•
The user-specified recalibration value will not be synchronized with the
INCREMENT BY numbering scheme. The specified value will be considered a
pure override.
SQL/MX Extensions to ALTER TABLE
The SQL/MX extensions are:
•
ATTRIBUTES clause
•
ASCENDING and DESCENDING options on the PRIMARY KEY constraint
Considerations for Referential Integrity
For information on referential integrity constraints, see the Considerations for
Referential Integrity section in CREATE TABLE.
Effects on TMF
Rename
After ANSI rename operations are performed, TMF recovery including backout,
volume, and file recovery are fully supported. TMF online dumps remain valid after
ANSI rename. Use the new ANSI names to access these dumps, because you can no
longer use the original ANSI names after rename is performed.
Effects on RDF
Rename
You must perform corresponding rename operations on the backup system to
synchronize primary and backup systems. This ensures that the logical
correspondence between the ANSI names are maintained in the primary and backup
databases.
Effects on open blown away
Rename
ANSI rename changes the redefinition timestamp of a table. Therefore, if there is an
open blown away after an ANSI rename operation, the similarity check will pass,