Drivers: Hashtype code in metadata may cause problems in front-end tools
Details
| Detail name | Value |
|---|---|
| Changelog Number | 11023 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | Exasol 7.0.0 |
| Fix Versions | Exasol 7.0.4 |
| Resolution Date | 2020-11-26 |
Description
For drivers ODBC, EXACLI (part of the EXA-SDK), JDBC, ADO.NET the current metadata code mapping to an non standard type may lead to issues on some BI frontends.
Workaround
There is no workaround
Fix
ODBC, EXACLI, JDBC and ADO.NET catalog tables will return the type code for CHAR, but type name in the catalog will be still HASHTYPE.
A HASHTYPE column from a result set will be shown as CHAR as well, but the native type and type name will be still HASHTYPE.
Explanation
The HASHTYPE is very similar to char in his representation. To improve the compatibility to many front end applications on the market, we decided to treat HASTYPE as CHAR for the applications.
The type info metadata functions of the drivers will also show CHAR and the type name HASHTYPE.
