You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Refactor redshift__get_columns_spec_ddl to use the new constraints data structure in favour of the existing constraints and constraints_check. Adapter specific tests should not need to change the existing expected_sql fixture is still the expected result!
Currently, redshift__get_columns_spec_ddl iterates over the user-provided columns and renders the constraint for each column constraint.
It does not render any check constraints because those are passed obtained col['constraints_check']. We should maintain this behaviour - constraints with type: check should not be rendered in the column spec ddl.
The text was updated successfully, but these errors were encountered:
github-actionsbot
changed the title
[Redshift] Use new ColumnLevelConstraint structure in redshift__get_columns_spec_ddl
[CT-2214] [Redshift] Use new ColumnLevelConstraint structure in redshift__get_columns_spec_ddl
Feb 28, 2023
Core issue: dbt-labs/dbt-core#7066
Refactor redshift__get_columns_spec_ddl to use the new
constraints
data structure in favour of the existingconstraints
andconstraints_check
. Adapter specific tests should not need to change the existingexpected_sql
fixture is still the expected result!Currently, redshift__get_columns_spec_ddl iterates over the user-provided columns and renders the constraint for each column constraint.
type
attribute of the newconstraints
data structure.check
constraints because those are passed obtainedcol['constraints_check']
. We should maintain this behaviour -constraint
s withtype: check
should not be rendered in the column spec ddl.The text was updated successfully, but these errors were encountered: