Linux ODBC/MX Client Driver for SQL/MX Release 3.2 (H06.25+, J06.14+)

Table 6 SQL/MP to ODBC/MX Date/Time Mappings (continued)
ODBC/MX data typeSQL/MP data type
SQL_TIMESTAMPDATETIME MINUTE TO FRACTION
SQL_TIMEDATETIME SECOND
SQL_TIMESTAMPDATETIME SECOND TO FRACTION
Microsoft escape clauses
ODBC/MX accepts Microsoft escape clauses and translates them into equivalent SQL/MX clauses.
For SQL/MX equivalents, see Table 7 (page 26).
Table 7 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 }
Supported{ call
procedure-name... }
Not supported{ escape 'escape-character' }
Not supported{ [?=]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 driver supports stored procedures, with the following exceptions:
• You must rewrite ODBC/MP stored procedures to SQL/MX stored procedures because SQL/MP
stored procedures are not converted to SQL/MX stored procedures.
• Results sets, pointers to cursors, and return codes are not supported.
For more information about stored procedures, see the SQL/MX Guide to Stored Procedures in
Java.
Transaction and cursor behavior
The transaction and cursor behavior is determined by the AUTOCOMMIT setting. For application
actions, see Table 8 (page 27).
26 Driver compatibility and considerations