Currently class ExasolSqlDialectin VSEXA overrides method AbstractSqlDialect .validateProperties() to perform additional validations for additional properties specific to this SQL dialect:
In future it should be sufficient to add validators to the existing validator chain already used by AbstractSqlDialect.
Currently this is not possible, since the chain is private.
The current ticket therefore proposes to add a protected method to class AbstractSqlDialect enabling each dialect to add additional property validators in its constructor.
VSEXA for example in method
Currently class
ExasolSqlDialect
in VSEXA overrides methodAbstractSqlDialect .validateProperties()
to perform additional validations for additional properties specific to this SQL dialect:https://github.com/exasol/exasol-virtual-schema/blob/main/src/main/java/com/exasol/adapter/dialects/exasol/ExasolSqlDialect.java#L140
In future it should be sufficient to add validators to the existing validator chain already used by
AbstractSqlDialect
. Currently this is not possible, since the chain is private. The current ticket therefore proposes to add a protected method to classAbstractSqlDialect
enabling each dialect to add additional property validators in its constructor.