SQL/MX 3.1 Reference Manual (H06.23+, J06.12+)

Introduction
HP NonStop SQL/MX Release 3.1 Reference Manual—663850-001
1-25
Naming Objects
The areas of support and the restrictions on access are:
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-60, 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
Naming Objects on
page 1-25
To refer to SQL/MP database objects, use either four-part
Guardian Physical Names
, three-part Logical Names, or
DEFINE Names
. To accommodate the use of ANSI names,
you must create Alias Mappings
from ANSI names to NSK
names.
Delimiting Reserved Words
in Guardian Names on
page 1-27
If a column or table name contains an SQL/MX reserved
word, you must delimit the reserved word in double quotes (").
Selecting or Changing Data
on page 1-27
You can select or change DATETIME Data, INTERVAL Data,
and NCHAR Data
with some restrictions.
Accessing Views
on
page 1-31
You can access both protection and shorthand views with the
same security as within NonStop SQL/MP.
Access Options
on
page 1-31
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-31
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-32
You cannot access SQL/MP tables that have specific file
organizations
Collations
on page 1-32 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.