Always use utf-8 characterset when importing text types and deprecate IMPORT_DATA_TYPES property (and value FROM_RESULT_SET)

exasol / virtual-schema-common-jdbc

Common module for JDBC-based access from Virtual Schemas

MIT License

0 stars 1 forks source link

Always use utf-8 characterset when importing text types and deprecate IMPORT_DATA_TYPES property (and value FROM_RESULT_SET) #157

Closed pj-spoelders closed 7 months ago

pj-spoelders commented 8 months ago

Part of our findings when testing v8, which now has strict datatype checking. These changes simplify and nullify edge case issues when importing text data using more esoteric charactersets in other DB systems (for example Latin1 Ü (umlauts), these don't fit in Exasol's version of ASCII, so UTF8 is required) The current switch that exists as a workaround for some of these edge cases is then also no longer needed.

pj-spoelders commented 7 months ago

Issues with project keeper after toolchains fix. Needs to be looked at by project keeper maintainers when they're available again. EDIT: found a solution