1  –  check-option-clause

    A constraint that places restrictions on update operations made
    to a view. The check option clause ensures that any rows that are
    inserted or updated in a view conform to the definition of the
    view. Do not specify the WITH CHECK OPTION clause with views that
    are read-only.

2  –  column-name

    A list of names for the columns of the view. If you omit column
    names, SQL assigns the names from the columns in the source
    tables in the select expression.

    However, you must specify names for all the columns of the view
    in the following cases:

    o  The select expression generates columns with duplicate names.

    o  The select expression uses statistical functions or arithmetic
       expressions to create new columns that are not in the source
       tables.

3  –  CONSTRAINT

    Specify a name for the WITH CHECK OPTION constraint. If you omit
    the name, SQL creates a name. However, Oracle Rdb recommends that
    you always name constraints. If you supply a name for the WITH
    CHECK OPTION constraint, the name must be unique in the schema.

    The name for the WITH CHECK OPTION constraint is used by the
    INTEG_FAIL error message when an INSERT or UPDATE statement
    violates the constraint.

4  –  select-expr

    A select expression that defines which columns and rows of the
    specified tables SQL includes in the view. The select expression
    for a nonmultischema database can name only tables in the same
    schema as the view. A select expression for a multischema
    database can name a table in any schema in the database; the
    schema need not be in the same catalog as the view being created.
    See the Select_Expressions HELP topic for more information on
    select expressions.

5  –  sql-and-dtr-clause

    Optional SQL and DATATRIEVE formatting clauses. See the
    DATATRIEVE HELP topic for more information on formatting clauses.

6  –  STORED_NAME_IS

    Specifies a name that Oracle Rdb uses to access a view created
    in a multischema database. The stored name allows you to access
    multischema definitions using interfaces, such as Oracle RMU,
    the Oracle Rdb management utility, that do not recognize multiple
    schemas in one database. You cannot specify a stored name for
    a view in a database that does not allow multiple schemas. For
    more details about stored names, see the User_Supplied_Names HELP
    topic.

7  –  view-name

    Name of the view definition you want to create. When choosing a
    name, follow these rules:

    o  Use a name that is unique among all view and table names in
       the schema.

    o  Use any valid SQL name (see the User_Supplied_Names HELP topic
       for more information).