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

ODBC/MX Conformance
HP NonStop ODBC/MX Driver for Windows—691126-003
5-12
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
Partial Date/Time Values

To use partial date/time values as parameters, provide values through the
ODBC/MX data type returned.

To fetch partial date/time values follow table SQL/MP to ODBC/MX Date/Time
Mappings on page 5-13. Partial date/time values fetched as character strings are
returned as partial even when the driver returns a full date/time/timestamp data
type. Default values are returned as a structure ( 1 for year/month/day, and 0 for
hour/minute/second/fraction).
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 5-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.0, when server side data source is
configured with
SQL_ATTR_MSACCESS_VERSION
flag
All unsigned types are promoted to the next signed
type.
Table 5-15. ODBC Data Types (page 3 of 3)
ODBC
Data Type
SQL/MX
Data Type
SQL/MP
Data Type
Supported by
ODBC/MX