ODBC Server Reference Manual

CORE SQL Language
HP NonStop ODBC Server Reference Manual—429151-002
3-4
Names
In the table-name shown above, table-identifier can be either a base-
table-identifier or a view-table-identifier.
Table 3-1 summarizes name format and how the NonStop ODBC Server handles
names.
All names created using the NonStop ODBC Server are converted to uppercase letters
before any SQL statement processing occurs. Therefore, names are not case
sensitive; “My_Table” is considered the same as “my_table” or “MY_TABLE.”
Table 3-2 summarizes the rules for creating CORE SQL identifiers, NonStop SQL/MP
simple names, and Guardian names.
Index-name [ [database.]owner. ] index-identifier
[ database.. ]
Procedure-name [ [database.]owner. ] procedure-identifier
[ database.. ]
Column-name [ {table-name }. ] column-identifier
[ {correlation-name} ]
Table 3-1. How the NonStop ODBC Server Maps CORE SQL Object Names
Name Type Name Format
How NonStop ODBC Server
Handles Name
Database name nodevolumesubvolume Maps it to \node.$volume.subvolume,
which corresponds to a NonStop SQL/MP
catalog.
Owner name logical-username Maps it to group-name.user-name, which
corresponds to a Guardian logon name.
Table name CORE SQL identifier* Maps it to an 8-character Guardian file
name.
Might resort to generating a random name.
View name CORE SQL identifier* Maps it to an 8-character Guardian file
name.
Might resort to generating a random name.
Index name CORE SQL identifier* Maps it to an 8-character Guardian file
name.
Might resort to generating a random name.
Procedure name CORE SQL identifier Maps it to a Pathway server class.
Column name CORE SQL identifier Maps it to a NonStop SQL/MP simple
name.
Correlation name CORE SQL identifier No mapping is required.
*The NonStop ODBC Server allows a maximum of 30 characters for table names, view names, and index names.