SQL/MX 3.2 Reference Manual (H06.25+, J06.14+)

Introduction
HP NonStop SQL/MX Release 3.2 Reference Manual—691117-001
1-26
Naming Objects
Naming Objects
Refer to SQL/MP database objects through MXCI or through applications by using
either physical names, logical names, or DEFINE names, as described next. For more
information, see Database Object Names on page 6-13, Object Naming on
page 10-62, or DEFINEs on page 6-38.
Physical Names
NonStop SQL/MP uses Guardian names as names for SQL tables, views, indexes,
partitions, collations, and program modules. A portion of the Guardian name (the
subvolume name) is used as an SQL/MP catalog name.
To provide flexibility, NonStop SQL/MX provides support for Guardian four-part object
names of the form:
[\node.][[$volume.]subvol.]filename
In this four-part name, \node is the name of a node on an HP NonStop system,
$volume is the name of a disk volume, subvol is the name of a subvolume, and
filename is the name of a Guardian disk file or the name of an SQL/MP table, view,
index, partition, collation, or program module.
For more information about Guardian name resolution, see Attribute Value NSK for
Guardian Names and Guardian Name Resolution on page 10-64.
Logical Names
To move toward full ANSI SQL:1999 compliance, NonStop SQL/MX provides support
for three-part logical object names of the form:
[[catalog.]schema.]name
Accessing Views on
page 1-32
You can access both protection and shorthand views with the
same security as within NonStop SQL/MP.
Access Options
on
page 1-32
You can use the SQL/MP access options as synonyms for
SQL/MX access options with some restrictions.
SQL/MP Stored Text
on
page 1-32
You cannot access or manipulate SQL/MP tables or views
that have been defined in specific ways. There are restrictions
on specific types of SQL/MP stored text.
SQL/MP File Organizations
on page 1-33
You cannot access SQL/MP tables that have specific file
organizations
Collations
on page 1-33 You cannot access any SQL/MP tables defined with collations
other than those tables defined with the default collation. You
cannot include the SQL/MP COLLATE option in a GROUP BY
clause or an ORDER BY clause when selecting from an
SQL/MP table.