Nonstop Database, HiRDB Version 9 UAP Development Guide
HiRDB uses the following two integrity constraints to ensure the validity of a database:
The NOT NULL constraint prohibits the null value from being set in a specified column.
The NOT NULL operand of the CREATE TABLE statement is used to implement the NOT NULL constraint. Because there must always be a value in every row of a column for which the NOT NULL constraint is specified, a constraint error occurs if an attempt is made to assign the null value in the column. When a constraint error occurs, the database cannot be updated; the null value must never be set in a column for which the NOT NULL constraint is specified.
When the uniqueness constraint is specified for a column, the value in every row of the column must be unique (no value can be duplicated in the column).
The uniqueness constraint can be specified for the following types of columns:
Specified with the UNIQUE operand of the CREATE TABLE statement.
For details about the cluster key specifications, see the HiRDB Version 9 Installation and Design Guide.
Specified with the UNIQUE operand of the CREATE INDEX statement.
For details about the CREATE TABLE and CREATE INDEX specifications, see the manual HiRDB Version 9 SQL Reference.
All Rights Reserved. Copyright (C) 2011, Hitachi, Ltd.