|
Problem IT35049
|
Status: Closed |
NEEDODBCTYPESONLY NOT WORKING AS DOCUMENTED
|
| product: |
IBM CSDK / 5724C2381 / 450 - CSDK 4.50 |
| Problem description: |
When the NEEDODBCTYPESONLY option is specific, the ODBC driver
should only describe and return Standard ODBC types.
The following table from the documentation describes what it
should return:
With Standard only this should be reported:
Table 3-1. Informix and ODBC data type mapping
Informix ODBC
Bigint SQL_BIGINT
Bigserial SQL_BIGINT
Blob SQL_LONGVARBINARY
Boolean SQL_BIT
Clob SQL_LONGVARCHAR
Int8 SQL_BIGINT
Lvarchar SQL_VARCHAR
Serial8 SQL_BIGINT
Multiset SQL_C_CHAR or SQL_C_BINARY
Set SQL_C_CHAR or SQL_C_BINARY
List SQL_C_CHAR or SQL_C_BINARY
Row SQL_C_CHAR or SQL_C_BINARY
That's not currently happening and could cause errors such as
"Unknown SQL type" from applications that can deal only with
standard ODBC types. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of Informix Client SDK prior to 4.50.FC6. *
****************************************************************
* PROBLEM DESCRIPTION: *
* When the NEEDODBCTYPESONLY option is specified, the ODBC *
* driver *
* should only describe and return Standard ODBC types. *
* The following table from the documentation describes what it *
* should return: *
* *
* With Standard only this should be reported: *
* Table 3-1. Informix and ODBC data type mapping *
* Informix ODBC *
* Bigint SQL_BIGINT *
* Bigserial SQL_BIGINT *
* Blob SQL_LONGVARBINARY *
* Boolean SQL_BIT *
* Clob SQL_LONGVARCHAR *
* Int8 SQL_BIGINT *
* Lvarchar SQL_VARCHAR *
* Serial8 SQL_BIGINT *
* Multiset SQL_C_CHAR or SQL_C_BINARY *
* Set SQL_C_CHAR or SQL_C_BINARY *
* List SQL_C_CHAR or SQL_C_BINARY *
* Row SQL_C_CHAR or SQL_C_BINARY *
* *
* That's not currently happening and could cause errors such *
* as *
* "Unknown SQL type" from applications that can deal only with *
* standard ODBC types. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Informix Client SDK 4.50.FC6 (when available). *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* Users of Informix Client SDK prior to 4.50.FC6. *
****************************************************************
* PROBLEM DESCRIPTION: *
* When the NEEDODBCTYPESONLY option is specified, the ODBC *
* driver *
* should only describe and return Standard ODBC types. *
* The following table from the documentation describes what it *
* should return: *
* *
* With Standard only this should be reported: *
* Table 3-1. Informix and ODBC data type mapping *
* Informix ODBC *
* Bigint SQL_BIGINT *
* Bigserial SQL_BIGINT *
* Blob SQL_LONGVARBINARY *
* Boolean SQL_BIT *
* Clob SQL_LONGVARCHAR *
* Int8 SQL_BIGINT *
* Lvarchar SQL_VARCHAR *
* Serial8 SQL_BIGINT *
* Multiset SQL_C_CHAR or SQL_C_BINARY *
* Set SQL_C_CHAR or SQL_C_BINARY *
* List SQL_C_CHAR or SQL_C_BINARY *
* Row SQL_C_CHAR or SQL_C_BINARY *
* *
* That's not currently happening and could cause errors such *
* as *
* "Unknown SQL type" from applications that can deal only with *
* standard ODBC types. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Informix Client SDK 4.50.FC6 (when available). *
**************************************************************** |
| Comment |
Fixed in Informix Client SDK 4.50.FC6. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 25.11.2020
06.01.2021
06.01.2021 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
