Microsoft escape clauses, Stored procedures, Transaction and cursor behavior – HP Integrity NonStop H-Series User Manual
Page 41

Table 8 SQL/MP to ODBC/MX Date/Time Mappings (continued)
ODBC/MX data type
SQL/MP data type
SQL_TIMESTAMP
DATETIME MINUTE TO FRACTION
SQL_TIME
DATETIME SECOND
SQL_TIMESTAMP
DATETIME SECOND TO FRACTION
SQL DATETIME RETRIEVAL
DATETIME VALUE RETRIEVAL
Microsoft escape clauses
ODBC/MX accepts Microsoft escape clauses and translates them into equivalent SQL/MX clauses.
lists the SQL/MX equivalents.
Table 9 SQL/MX equivalents for Microsoft escape clauses
SQL/MX equivalent
Microsoft 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-string
interval-string
interval-qualifier
interval-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 drivers support NonStop SQL/MX stored procedures, with the following exceptions:
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.
lists
the transaction and cursor behavior.
Microsoft escape clauses
41