Linux ODBC/MX Client Driver for SQL/MX Release 3.2.1 (H06.26+, J06.15+)

Table 5 ODBC Data Types (continued)
Supported by the driver?SQL/MP data TypeSQL/MX data TypeODBC data type
NoNot supportedNot supportedTINYINT UNSIGNED
YesLARGEINTLARGEINTBIGINT
NoNot supportedNot supportedBINARY(n)
NoNot supportedNot supportedVARBINARY(n)
NoNot supportedNot supportedLONG VARBINARY
YesDATEDATEDATE
YesTIMETIMETIME(p)
YesTIMESTAMPTIMESTAMPTIMESTAMP
YesINTERVAL MONTH(p)INTERVAL MONTH(p)
YesINTERVAL YEAR(p)INTERVAL YEAR(p)
YesINTERVAL YEAR(p) TO
MONTH
INTERVAL YEAR(p) TO
MONTH
YesINTERVAL DAY(p)INTERVAL DAY(p)
YesINTERVAL HOUR(p)INTERVAL HOUR(p)
YesINTERVAL MINUTE(p)INTERVAL MINUTE(p)
YesINTERVAL SECOND(p)INTERVAL SECOND(p)
YesINTERVAL DAY(p) TO HOURINTERVAL DAY(p) TO HOUR
YesINTERVAL DAY(p) TO
MINUTE
INTERVAL DAY(p) TO
MINUTE
YesINTERVAL DAY(p) TO
SECOND
INTERVAL DAY(p) TO
SECOND
YesINTERVAL HOUR(p) TO
MINUTE
INTERVAL HOUR(p) TO
MINUTE
YesINTERVAL HOUR(p) TO
SECOND(q)
INTERVAL HOUR(p) TO
SECOND(q)
YesINTERVAL MINUTE(p) TO
SECOND(q)
INTERVAL MINUTE(p) TO
SECOND(q)
* 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 the unsigned
numeric data type, use the SQLBindParameter API to insert the data and the SQLBindCol API
to select the data with the SQL_C_CHAR data type.
Unsigned data types
The behavior of unsigned data types is determined by the ODBC version and the
SQL_ATTR_MSACCESS_VERSION flag setting. Table 6 (page 25) explains the behaviors of
unsigned data types.
24 Driver compatibility and considerations