Database Object Names; Logical Names For Sql Objects; Sql Object Namespaces - HP Neoview SQL Reference Manual

Hide thumbs Also See for Neoview SQL:
Table of Contents

Advertisement

Database Object Names

"Logical Names for SQL Objects"

"SQL Object Namespaces"

DML statements can refer to Neoview SQL database objects. To refer to a database object in a
statement, use an appropriate database object name. For information on the types of database
objects see
"Database Objects" (page
Logical Names for SQL Objects
You may refer to an SQL table, view, or procedure by using a one-part or two-part logical name,
also called an ANSI name:
schema-name.object-name
In this two-part name, schema-name is the name of the schema, and object-name is the simple
name of the table or view. Each of the parts is an SQL identifier. See
Neoview SQL automatically qualifies an object name with the schema name unless you explicitly
specify schema names with the object name. A one-part name object-name is qualified implicitly
with the default schema.
You can qualify a column name in a Neoview SQL statement by using a two-part or one-part
object name, or a correlation name.
SQL Object Namespaces
Neoview SQL objects are organized in a hierarchical manner. Database objects exist in schemas,
which are themselves contained in catalogs. Catalogs are collections of schemas. Schema names
must be unique within the Neoview catalog.
Multiple objects with the same name can exist provided that each belongs to a different namespace.
Neoview SQL supports these namespaces:
Constraint
Index
Lock
Materialized view logs
Schema label
Sequence generator
Table value object (table, view, procedure)
Trigger
Trigger temporary table
Objects in one schema can refer to objects in a different schema. Objects of a given namespace
are required to have unique names within a given schema.
242
SQL Language Elements
241).
"Identifiers" (page
269).

Advertisement

Table of Contents
loading

Table of Contents