Closed exaSR closed 1 year ago
@redcatbear and @ckunki propose to update the VSEXA to
SCHEMA_NAME
mandatory.SCHEMA_NAME
Rationale: Whether the property SCHEMA_NAME
is mandatory or not depends on the specific dialect of JDBC-based virtual schema.
I therefore moved the issue from VSCJDBC to the current repo.
Tested this using exasol-virtual-schema, but I assume this is a problem in the jdbc implementation already...
setup
Bug 1: Metadata for tables with same name is just mashed together
results in
Bug 2: Generated SQL is not schema-qualified
results in
because: