Open System Services ODBC/MX Client Driver for SQL/MX Release 3.1 (H06.23+, J06.12+)

ODBC/MX Conformance
HP NonStop Open System Services ODBC/MX Client Driver for SQL/MX Release 3.1—663857-001
3-11
Unsigned Data Types
Unsigned Data Types
Unsigned data types are treated differently, according to the version of ODBC used,
and whether the SQL_ATTR_MSACCESS_VERSION flag is set
INTERVAL MONTH(p) INTERVAL MONTH(p)Yes
INTERVAL YEAR(p) INTERVAL YEAR(p)Yes
INTERVAL YEAR(p) TO
MONTH
INTERVAL YEAR(p) TO
MONTH
Yes
INTERVAL DAY(p)INTERVAL DAY(p)Yes
INTERVAL HOUR(p) INTERVAL HOUR(p)Yes
INTERVAL MINUTE(p) INTERVAL MINUTE(p)Yes
INTERVAL SECOND(p) INTERVAL SECOND(p)Yes
INTERVAL DAY(p) TO
HOUR
INTERVAL DAY(p) TO
HOUR
Yes
INTERVAL DAY(p) TO
MINUTE
INTERVAL DAY(p) TO
MINUTE
Yes
INTERVAL DAY(p) TO
SECOND
INTERVAL DAY(p) TO
SECOND
Yes
INTERVAL
HOUR(p) TO MINUTE
INTERVAL
HOUR(p) TO MINUTE
Yes
INTERVAL HOUR(p) TO
SECOND(q)
INTERVAL HOUR(p) TO
SECOND(q)
Yes
INTERVAL MINUTE(p) TO
SECOND(q)
INTERVAL MINUTE(p)
TO SECOND(q)
Yes
* The VARCHAR length can be up to 4059 for key-sequenced files or
4070 for entry-sequenced files.
** Starting with SQL/MX Release 3.0, the precision of the NUMERIC data type is extended to 128
digits. If the precision is greater than 18 for signed and greater than 9 for unsigned numeric data type,
use the SQLBindParameter function to insert the data and the SQLBindCol function to select the data
with the SQL_C_CHAR data type.
Table 3-16. Behavior of Unsigned Data Types
ODBC Version Behavior of Unsigned Data Types
2.0 UNSIGNED SMALLINT promoted to SIGNED INT
UNSIGNED INT promoted to BIGINT
3.x, when server side data source is
configured with
SQL_ATTR_MSACCESS_VERSION
flag
All unsigned types are promoted to the next signed
type.
Table 3-15. ODBC Data Types (page 2 of 2)
ODBC
Data Type
SQL/MX
Data Type
SQL/MP
Data Type
Supported by
ODBC/MX