NonStop SQL/MP Reference Manual

NonStop SQL/MP Reference Manual—142115
S-68
Exceptions to Conformance With Entry Level SQL
1992
NonStop SQL/MP table names are Guardian names, which allow a node and disk
specification where ANSI/ISO SQL allows catalog. Guardian names also allow
what NonStop SQL/MP calls a catalog where ANSI/ISO SQL allows schema.
•
Security
The ANSI/ISO SQL security model differs overall from the Guardian security
model (including the optional Safeguard security product) used by NonStop
SQL/MP. Because of the differences in the model, NonStop SQL/MP does not
implement table privileges (SELECT, INSERT, UPDATE, DELETE, and
REFERENCES), column privileges (UPDATE and REFERENCES), or the USER
value.
ANSI/ISO SQL defines authorization with the GRANT and REVOKE statements.
NonStop SQL/MP uses the ALTER statements and the SECURE command.
•
Constraints
ANSI/ISO SQL allows you to define a unique constraint when you create a table or
to provide a UNIQUE qualifier on a column definition. To achieve a unique
constraint in NonStop SQL/MP, you specify a unique column as the primary key of
a table or create a unique index on a column.
NonStop SQL/MP does not allow you to qualify a constraint name with a catalog
and schema name.
NonStop SQL/MP does not support the FOREIGN KEY table constraint or the
REFERENCES column constraint.
•
Views
ANSI/ISO SQL allows you to update a view if the query that defines the view can
be updated. NonStop SQL/MP defines two types of views: protection views that can
be updated and shorthand views that cannot be updated.
ANSI/ISO SQL allows you to create views on views. NonStop SQL/MP allows you
to create views on shorthand views, but not on protection views.
ANSI/ISO SQL provides a SELECT DISTINCT clause on the CREATE VIEW
statement and allows a WHERE clause in a view definition to refer to columns that
are not in the select list. NonStop SQL/MP does not provide such a clause.
•
Statement atomicity and transaction definition
ANSI/ISO SQL provides both statement atomicity (all changes made during a
multirecord operation are canceled if an error occurs during the operation) and
implicit transaction beginnings.
In NonStop SQL/MP, audited tables have equivalent protection for a TMF
transaction but not for a single statement. You must explicitly begin each transaction
within a program, and you must explicitly begin any multistatement transactions
entered through SQLCI.
NonStop SQL/MP protects audited tables by requiring DML statements within
programs to occur within explicitly defined transactions; however, NonStop