SQL/MX 2.x Reference Manual (H06.10+, J06.03+)

SQL/MX Statements
HP NonStop SQL/MX Reference Manual544517-008
2-85
Syntax Description of CREATE TABLE
referenced-table, the referencing column(s) of the referencing row
from the referencing table is set to its DEFAULT value.
referenced-table is the table referenced by the foreign key in a referential
constraint. referenced-table cannot be a view. referenced-table
cannot be the same as table.
column-list specifies the column or set of columns in referenced-table
that corresponds to the foreign key in table. The columns in the column list
associated with REFERENCES must be in the same order as the columns in
the column list associated with FOREIGN KEY. If column-list is omitted, the
referenced table’s PRIMARY KEY columns are the referenced columns.
A table can have an unlimited number of referential constraints, and you can
specify the same foreign key in more than one referential constraint, but you must
define each referential constraint separately. You cannot create self-referencing
foreign key constraints.
Publish/Subscribe's embedded update and embedded delete statements are not
allowed on tables with referential integrity constraints:
STORE BY store-option
specifies a set of columns on which to base the clustering key. The clustering key
determines the order of rows within the physical file that holds the table. The
storage order has an effect on how you can partition the object.
store-option is defined as:
PRIMARY KEY
bases the clustering key on the primary key columns. This store option
requires that the primary key is NOT DROPPABLE. If the primary key is
defined as DROPPABLE, NonStop SQL/MX returns an error.
key-column-list
bases the clustering key on the columns in the key-column-list. The key
columns in key-column-list must be specified as NOT NULL NOT
DROPPABLE and cannot have a combined length of more than 247 bytes.
The default is PRIMARY KEY if you specified a PRIMARY KEY clause that has the
NOT DROPPABLE constraint in the CREATE TABLE statement.
If you omit the STORE BY clause and you do not specify a PRIMARY KEY that
has the NOT DROPPABLE constraint, the storage order is determined only by the
SYSKEY. You cannot partition a table stored only by SYSKEY. See SYSKEYs on
page 6-60.
Note. The referential actions CASCADE, SET NULL, and SET DEFAULT are
available only on systems running J06.09 and later J-series RVUs and H06.20 and
later H-series RVUs.