ODBC/MX Driver for Windows Manual for SQL/MX Release 3.2.1 (H06.26+, J06.15+)

ODBC/MX Conformance
HP NonStop ODBC/MX Driver for Windows—691126-002
5-14
Microsoft Escape Clauses
Microsoft Escape Clauses
ODBC/MX accepts Microsoft escape clauses and translates them into equivalent
SQL/MX clauses.
Stored Procedures
A stored procedure is a type of user-defined routine (UDR) that operates within a
database server and typically performs SQL operations on a database. ODBC/MX
supports stored procedures, with the following exceptions:

ODBC/MP does not support Result sets for stored procedures in java and
therefore cannot be converted to ODBC/MX procedures. They must be rewritten.

Returning codes are not supported.
ODBC/MX supports Stored procedures that return Result Sets and also supports
pointers to cursors on systems running J06.05 or later J-series RVUs and H06.16 and
later H-series RVUs.
For more information about stored procedures, see the SQL/MX Guide to Stored
Procedures in Java.
Table 5-18. Microsoft Escape Clauses
Microsoft Escape Clause SQL/MX Equivalent
{ d 'date-literal' } DATE 'date-literal'
{ t 'time-literal' } TIME 'time-literal'
{ ts 'timestamp-literal' } TIMESTAMP 'timestamp-literal'
1
{ oj join-expression } join-expression
{ INTERVAL sign
interval-string
interval-qualifier }
INTERVAL sign
interval-string
interval-qualifier
{ fn scalar-function } scalar-function
2
{ call
procedure-name... }
Supported in current release
{ escape 'escape-character' } Not supported in the current release.
{ [?=]call
procedure-name... }
Not supported in the current release.
1. ODBC syntax does not include nested joins, while SQL/MX does. ODBC/MX extends the Microsoft syntax for
an outer join.
2. Functions are controlled by SQLGetInfo. Only SQL/MX native functions are supported.