Closed exaSR closed 1 year ago
I think the changes with VSEXA 7.1.0 and VSCJDBC 10.3.0 already fixed this problem. In the scope of the current ticket I will add an additional integration test, though:
@Test
void testAlterVirtualSchemaTriggersPropertyValidation() throws SQLException {
this.virtualSchema = createVirtualSchema(this.sourceSchema);
final String name = this.virtualSchema.getFullyQualifiedName();
final SQLException exception = assertThrows(SQLException.class,
() -> query("alter virtual schema {0} set EXA_CONNECTION = Null", name));
final String expected = PropertyValidationException.class.getName() + ": E-VSCJDBC-17";
assertThat(exception.getMessage(), containsString(expected));
}
EXA_CONNECTION
CREATE VIRTUAL SCHEMA
ALTER VIRTUAL SCHEMA
ALTER VIRTUAL SCHEMA
, tooOriginal report
Adapter Version
virtual-schema-dist-10.1.0-exasol-7.0.2
Semantic check for EXA_CONNECTION parameter is active for CREATE:
yields error message
But not for ALTER:
-->
(related with #89: once IMPORT_FROM_EXA is set, it can not be disabled)