Uniform Metadata for DOUBLE Data Type Across ODBC APIs Now Ensured
Details
| Detail name | Value |
|---|---|
| Changelog Number | 24666 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | Exasol 7.1.0 |
| Fix Versions | ODBC 25.2.3 |
| Resolution Date | 2025-06-20 |
Description
The ODBC driver incorrectly assigned the column metadata data type name DOUBLE for result-set columns with the DOUBLE data type.
- SQLColAttribute (SQL_COLUMN_TYPE_NAME or SQL_DESC_TYPE_NAME) returned DOUBLE, whereas metadata queried using other APIs like SQLColumns and SQLGetTypeInfo correctly returned DOUBLE PRECISION.
- This inconsistency caused confusion for applications relying on accurate metadata and schema definitions across ODBC APIs.
Workaround
Use the SQLColumns , SQLGetTypeInfo, or SQLColAttribute(SQL_DESC_CONCISE_TYPE)
Fix
- The ODBC driver has been updated to ensure that SQLColAttribute returns the correct data type name, DOUBLE PRECISION, for columns with the DOUBLE data type.
- Now, SQLColAttribute behavior is consistent with SQLColumns and SQLGetTypeInfo, providing reliable metadata across all APIs.
Changed behavior
Before the Fix: SQLColAttribute returned DOUBLE for the DOUBLE data type in columns, leading to inconsistent metadata compared to SQLColumns and SQLGetTypeInfo. Applications relying on SQLColAttribute might have misinterpreted the column data type as DOUBLE, while DOUBLE PRECISION is the correct name. After the Fix: SQLColAttribute now returns DOUBLE PRECISION for columns of the DOUBLE data type. All APIs (SQLColAttribute, SQLColumns, SQLGetTypeInfo) consistently report DOUBLE PRECISION for DOUBLE columns, eliminating ambiguity.
