fix: EXPOSED-151 Quoted identifiers cause incorrect schema validation #1842
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If a table object is created with user-quoted table and/or column names, attempting to validate it using either
SchemaUtils.createMissingTablesAndColumns()
orSchemaUtils.statementsRequiredToActualizeScheme()
incorrectly generates CREATE and ALTER statements.This happens because metadata returned by the database does not generally include quotes.
So any comparison check with the cached identifiers (which do include quotes) in
Table.exists()
orSchemaUtils
functions causes false negative results.Table and column functions that process/unquote the respective names are introduced to ensure a more accurate equality check with metadata.