Open System Services ODBC/MX Client Driver Manual for SQL/MX Release 3.2.1 (H06.26+, J06.15+)

Microsoft Escape Clauses
ODBC/MX accepts Microsoft escape clauses and translates them into equivalent SQL/MX clauses.
Table 20 SQL/MX equivalents for Microsoft escape clauses
SQL/MX equivalentMicrosoft escape clause
DATE 'date-literal'{ d 'date-literal' }
TIME 'time-literal'{ t 'time-literal' }
TIMESTAMP 'timestamp-literal' *{ ts 'timestamp-literal' }
join-expression{ oj join-expression }
INTERVAL sign{ INTERVAL sign
interval-stringinterval-string
interval-qualifierinterval-qualifier }
scalar-function **{ fn scalar-function }
scalar-function **{ fn scalar-function }
Supported in current release{ call
procedure-name... }
Not supported in the current release.{ escape 'escape-character' }
Not supported in the current release.{ [?=]call
procedure-name... }
* ODBC syntax does not include nested joins, while SQL/MX does. ODBC/MX extends the
Microsoft syntax for an outer join.
** Functions are controlled by SQLGetInfo. Only SQL/MX native functions are supported.
Stored Procedures
The OSS ODBC/MX Client Driver supports stored procedures, with the following exceptions:
• ODBC/MP stored procedures cannot be converted to ODBC/MX procedures. They must be
rewritten.
• Results sets, pointers to cursors, and returning codes are not supported.
For more information about stored procedures, see the SQL/MX Guide to Stored Procedures in
Java.
Transactions and Cursor Behavior with Multiple Statements
Table 21 Transactions and Cursor Behavior
Action RequiredSQL/MX BehaviorAutocommit
N.A.When any open statement reaches
end of data or end of cursor, SQL/MX
closes all other open statements.
ON
The application must explicitly rollback
or commit the transaction. All open
statements are closed at that time.
N.A.OFF
Microsoft Escape Clauses 41