SQL/MP to SQL/MX Database and Application Migration Guide

Converting SQL/MP Applications to SQL/MX
Applications
HP NonStop SQL/MP to NonStop SQL/MX Database and Application Migration Guide—666211-001
4-27
SQL Functions
COUNT Yes No changes are required for NonStop SQL/MX.
CURRENT Yes, but
changes
might be
required.
The SQL/MX CURRENT function cannot return
a subset of date-time fields. CURRENT always
returns year-to-second data. To return a
different range of date-time fields, use one of
the SQL/MX date-time functions. For more
information, see Date-Time Data Types and
Literals on page 4-35.
CURRENT_TIMESTAMP Yes No changes are required for NonStop SQL/MX.
For more information, see Date-Time Data
Types and Literals on page 4-35.
DATEFORMAT Yes No changes are required for NonStop SQL/MX.
For more information, see Date-Time Data
Types and Literals on page 4-35.
DAYOFWEEK Yes No changes are required for NonStop SQL/MX.
For more information, see Date-Time Data
Types and Literals on page 4-35.
EXTEND No Remove this function from the source code,
and use the CAST function instead. For more
information, see the SQL/MX Reference
Manual.
JULIANTIMESTAMP Yes No changes are required for NonStop SQL/MX.
For more information, see Date-Time Data
Types and Literals on page 4-35.
MAX Yes No changes are required for NonStop SQL/MX.
MIN Yes No changes are required for NonStop SQL/MX.
OCTET_LENGTH Yes NonStop SQL/MP and NonStop SQL/MX differ
somewhat in how they handle particular types
of character strings. See Character Sets
on
page 4-34.
POSITION Yes NonStop SQL/MP and NonStop SQL/MX differ
somewhat in how they handle particular types
of character strings. See Character Sets
on
page 4-34.
SETSCALE No Remove this function from the source code. In
an embedded SQL/MX application, you provide
the scale when you declare the host variables.
For more information, see SETSCALE Function
on page 4-42.
Table 4-7. SQL/MX and SQL/MP Functions (page2of3)
SQL/MP Functions
Implemented
in SQL/MX? Comments