fix(targets): Quote add-column-ddl with column starting with _
(underscore) based on engine
#2583
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.
Description
Pass the compiled string output to the DDL element constructor.
This ensures that the compilation is engine specific and engine specific quoting rules are respected.
Passing the compiler element to the context
sa.DDL
does not yield proper engine-specific quoting.Some databases (e.g. IBM Db2, and maybe others as well) require fields starting with underscore (e.g.
_id
) to be quoted, while other databases (postgres, sqlite) accept fields with leading underscores without quotes.Testing
Updated schema evolution test in
testing/target_test_streams
to ensure any downstream target is also tested for scenario:add column starting with underscore
.Added scenario:
add column starting with underscore
to the sqlite sample target test.📚 Documentation preview 📚: https://meltano-sdk--2583.org.readthedocs.build/en/2583/