search

exasol / exasol-virtual-schema

Virtual Schema from Exasol to Exasol
MIT License
1 stars 2 forks source link

Fix escaping wildcards when looking up column metadata #99

Closed ckunki closed 1 year ago

ckunki commented 1 year ago

In https://github.com/exasol/virtual-schema-common-jdbc/pull/139 VSCJDBC was changed to escape wildcards when looking up column metadata.

This worked fine for VSEXA as demonstrated by a related test but caused failures with other JDBC drivers, e.g. in VSORA, see https://github.com/exasol/oracle-virtual-schema/issues/30.

In https://github.com/exasol/virtual-schema-common-jdbc/issues/142 therefore the change in VSCJDBC was rolled back with release 10.5.0 but at the same time providing a method that SQL dialects inheriting from VSCJDBC can override in order to escape wildcards.

To enable wildcard escaping again in VSEXA after updating to VSCJDBC 10.5.0, VSEXA needs to be changed again to implement the wild card escaping individually.

ckunki commented 1 year ago

Wild card escaping has been fixed and improved in VSCJDBC release 10.5.0. Behavior and interface is unchanged from perspective of VSEXA. Next release of VSEXA may still update dependency to VSCJDBC to 10.5.0. Closing current ticket.