SQL/MP Reference Manual

HP NonStop SQL/MP Reference Manual—523352-013
C-169
Considerations—CREATE VIEW
You must also ensure that purge authority includes the users with authority to
purge the underlying table. For a shorthand view, only purge authority has
meaning, although you must specify a complete security string. Anyone with
authority to read the underlying tables and views can also read the shorthand view.
For information, see Security on page S-11.
WITH CHECK OPTION
specifies that no row can be placed in the database through the view unless the
row satisfies the view definition. WITH CHECK OPTION applies only to protection
views. If you omit this option, a newly inserted row or an updated row need not
satisfy the view definition, which means that such a row can be inserted in the
table but it does not appear in the view.
WITH CHECK OPTION does not affect select-statement; rows must always
satisfy the view definition in this case.
WITH HEADINGS
specifies that the heading for a view column is inherited from the underlying table
or view column from which the new view column is derived. If you specify the
HEADING or NO HEADING clause in new-column-name, no heading is inherited.
A view column that is a function or an expression cannot inherit a heading.
WITH HELP TEXT
specifies that help text for a view column is inherited from an underlying base table
or view. A view column that is a function or an expression cannot inherit help text.
Considerations—CREATE VIEW

CREATE VIEW requires 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 the 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 write access for a protection view,
you must have authority to write to the underlying table and all associated indexes
unless you are the super ID. To specify read access for a protection view, you must
have authority to read the underlying table and all associated indexes unless you
are the super ID. For protection views managed by SMF, view must be the same
type of name, virtual or direct, as the underlying table.
Only one DDL statement can operate on a given SQL object (or partition of an SQL
object) at a time. An error occurs if you attempt to execute a CREATE VIEW
statement while another process is executing a DDL operation on the same object.
The specific error depends on the DDL operation involved and the phase of the
operation at which the conflict occurs. (For more information, see DDL (Data
Definition Language) Statements on page D-20.)