Skip to content

4.1.0: Configurable datatype detection
Compare
Choose a tag to compare
@ckunki ckunki released this 05 Dec 12:36
· 8 commits to main since this release
4.1.0
9ec0f09
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Summary

Virtual-schema-common-jdbc version 10.0.0 introduced enhanced detection for data types of result sets.

Unfortunately with the new algorithm compatibility problems with the source database can happen under the following circumstances:

  • data type CHAR or VARCHAR
  • 8-bit character sets with encodings like latin1 or ISO-8859-1
  • characters being not strictly ASCII, e.g. German umlaut "Ãœ"

The current release therefore uses an updated version of virtual-schema-common-jdbc with an additional adapter property to configure the data type detection.

For details please see adapter Properties for JDBC-Based Virtual Schemas.

Bugfixes

  • #26: Enabled to use MySQL database with character set latin1 and characters not strictly ASCII.

Dependency Updates

Compile Dependency Updates

  • Updated com.exasol:virtual-schema-common-jdbc:10.0.1 to 10.1.0

Test Dependency Updates

  • Updated com.exasol:exasol-testcontainers:6.3.1 to 6.4.0
  • Updated com.exasol:virtual-schema-common-jdbc:10.0.1 to 10.1.0
Assets 5
Loading