Ticket #120 introduced enhanced detection for data types of result sets based on metadata of the connection and calculated by Exasol database available with Exasol 7.1.14, Exasol 8.6.0 and above.
Recently problems have been reported
character set latin1 and
data values not strictly ASCII, e.g. German umlaut "Ü".
... for the following virtual schemas:
Schema
Version (a)
Version (b)
Ticket
VSMYSQL
3.0.0
4.0.0
exasol/mysql-virtual-schema#26
VSORA
2.2.2
2.3.0
The current ticket therefore requests to add support for an optional parameter to deactivate data type calculation by Exasol database and to infer the data types from the values in the result set as implemented until version (a) of the respective virtual schemas even if the Exasol database supports the new alternative.
Ticket #120 introduced enhanced detection for data types of result sets based on metadata of the connection and calculated by Exasol database available with Exasol 7.1.14, Exasol 8.6.0 and above.
Recently problems have been reported
The current ticket therefore requests to add support for an optional parameter to deactivate data type calculation by Exasol database and to infer the data types from the values in the result set as implemented until version (a) of the respective virtual schemas even if the Exasol database supports the new alternative.