SQL/MX Programming Manual for Java

SQL/MX Programming Considerations
HP NonStop SQL/MX Programming Manual for Java—523726-003
4-25
RDF Considerations
To enable easier deployment of SQLJ applications in an RDF environment, follow
these guidelines:
•
SQL/MP Object Names for an RDF Environment on page 4-25
•
SQL/MX Object Names for an RDF Environment on page 4-25
SQL/MP Object Names for an RDF Environment
When referring to SQL/MP objects in an SQLJ program, use class MAP DEFINEs or
SQL/MP aliases. See DEFINE Names for SQL/MP Objects on page 4-21 and SQL/MP
Aliases for SQL/MP Objects on page 4-21. If you refer to SQL/MP aliases in the
program, use partially qualified names by omitting the catalog name. See SQL/MX
Object Names for an RDF Environment on page 4-25.
If you use hard-coded Guardian names, omit the node name from the table name,
letting the node default to the node on which the program is customized. See Guardian
Names for SQL/MP Objects on page 4-21.
SQL/MX Object Names for an RDF Environment
When referring to SQL/MX objects in an SQLJ program, use partially qualified names
by omitting the catalog name (for example, sch.tab or tab). See ANSI Names for
SQL/MX Objects on page 4-20.
Do not embed DECLARE, SET, or CONTROL QUERY DEFAULT statements that
qualify the object names. Instead, qualify the object names on the SQLJ command line
by using the -catalog or -schema options during customization. For more
information, see -catalog on page 5-30 and -schema on page 5-31.
If the program queries database objects in multiple catalogs, associate a unique
connection context with statements that belong to a particular catalog. Each connection
context class produces a profile that contains statements associated with a particular
catalog. You can then customize each profile individually with a different -catalog or
-schema setting. For more information, see Generating a Profile for Each Connection
Context Class on page 3-17.