SQL/MX 2.x Database and Application Migration Guide (G06.23+, H06.04+, J06.03+)

Converting SQL/MP Applications to SQL/MX
Applications
HP NonStop SQL/MX Database and Application Migration Guide—540435-005
10-31
Database Object References
Database Object References
SQL/MX applications can refer to SQL/MX database objects and most SQL/MP
database objects. When converting an SQL/MP application to an SQL/MX application,
follow these guidelines for database object references:
•
Database Object References That Are Disallowed in NonStop SQL/MX on
page 10-31
•
SQL/MP Database Object References on page 10-32
•
SQL/MX Database Object References on page 10-32
Database Object References That Are Disallowed in
NonStop SQL/MX
An SQL/MX application cannot refer to SQL/MP database objects that are defined in a
particular way. NonStop SQL/MX restricts specific types of SQL/MP stored text, which
is SQL text that NonStop SQL/MX retrieves from the SQL/MP catalog while processing
SQL/MX text. SQL/MP stored text includes views, constraints, column defaults, first
keys, clustering keys, and partitioning keys.
SQL/MX applications cannot refer to views that have these characteristics or to
SQL/MP database objects with constraints, column defaults, first keys, clustering keys,
and partitioning keys that contain:
•
UNITS function
•
DATETIME string portions with nonstandard formatting
•
FRACTION-only DATETIME or INTERVAL literals or columns
•
Interval literals with negative signs inside quotation mark delimiters (for example,
INTERVAL '-5' DAY)
•
Identifiers that use SQL/MX reserved words
SQL/MX applications cannot refer to SQL/MP tables that have these characteristics:
•
Partitioned, entry-sequenced file organization
•
Relative file organization
•
Collations other than the default collation (using the binary value of characters in a
column)
SQL/MX applications cannot select from, insert, or update columns with FRACTION-
only DATETIME or INTERVAL values. For more information, see the
SQL/MX
Reference Manual.
If your SQL/MP application refers to SQL/MP database objects that are defined in
these ways, reconsider converting the application to NonStop SQL/MX, or consider
converting the SQL/MP database objects to SQL/MX database objects. For more
information, see Section 11, Converting an SQL/MP Database to SQL/MX Tables
.