SQL/MX Comparison Guide for SQL/MP Users

Data Definition Language (DDL) Differences
HP NonStop SQL/MX Comparison Guide for SQL/MP Users—523735-003
6-6
Views
NonStop SQL/MP allows no more than one partition of an object on each disk.
SQL/MP partitions have Guardian names.
You manage partitions differently in NonStop SQL/MX and NonStop SQL/MP. For
details, see Partition Management: The MODIFY Utility on page 7-2
Views
SQL/MX Views
The distinction between protection and shorthand views does not exist for SQL/MX
views. To create a view, you must have SELECT privileges for the objects underlying
the view.
NonStop SQL/MX supports UNION in a view definition.
For information about SQL/MX views, see “SQL/MX Language Elements” in the
SQL/MX Reference Manual.
SQL/MP Views
An SQL/MP view is either a protection view or a shorthand view. A protection view is
derived from a single table and can be read, updated, and secured. A shorthand view
is derived from one or more tables or other views and inherits the security of the
underlying tables. A shorthand view can be read but not updated.
To create a view, you must have authority to write to the catalog that receives the view
description and to the USAGES tables of catalogs describing the underlying tables and
views.
To create a protection view, you must also be a generalized owner of the underlying
table. Any partitions or indexes of the table underlying the protection view must be
accessible when you create the view. To specify read or write access for a protection
view, you must have authority to read or write to the underlying table and all associated
indexes (unless you are the super ID).
NonStop SQL/MX and NonStop SQL/MP handle security on views differently. In
NonStop SQL/MP, you need to have appropriate security on the underlying tables of
the view in order to update the view. In NonStop SQL/MX you need only to have
appropriate security on view itself. You do not need to have privileges on the
underlying table.
For information about SQL/MP views, see Views in the SQL/MP Reference Manual.
Object Security
NonStop SQL/MX uses GRANT and REVOKE statements that conform to the ANSI
SQL standard to control privileges for objects. It does not support a SECURE clause.
Security is controlled internally by the software and does not use the security vector.