From cf1dba4bc8c2e0f36c80a53a033969ca9f8cf0e1 Mon Sep 17 00:00:00 2001 From: Christoph Kuhnke Date: Tue, 6 Dec 2022 09:30:01 +0100 Subject: [PATCH] fixed UTF8 encoding (#28) --- doc/changes/changes_2.4.0.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/changes/changes_2.4.0.md b/doc/changes/changes_2.4.0.md index 6b3b5dd..a170d5d 100644 --- a/doc/changes/changes_2.4.0.md +++ b/doc/changes/changes_2.4.0.md @@ -1,4 +1,4 @@ -# Virtual Schema for Oracle 2.4.0, released 2022-12-05 +# Virtual Schema for Oracle 2.4.0, released 2022-12-06 Code name: Dependency Upgrade @@ -12,7 +12,7 @@ Unfortunately with the new algorithm compatibility problems with the source data * 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 "Ü" +* 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.