Open victor-frank-signet opened 1 month ago
This is probably no longer a bug. This was resolved on my end by changing the permissions on the view and the table, then dbt could resolve they are not external. But I still think this at least an enhancement but maybe a bug because if the view exists but dbt user does not have permission it should not produce a invalid sql "drop external if " instead it should say permission error while running the correct redshift sql stament "drop view|table if"
It has something to do with how the relation.type is populated in: �[0m00:11:30 Redshift adapter: Error running SQL: macro drop_relation
Is this a new bug in dbt-redshift?
Current Behavior
When creating a view in redshift with jinja.
The produced code is creating a a temp view and then sometimes running
drop external if
which is not valid redshift syntax:Expected Behavior
Compiles to:
Steps To Reproduce
Relevant log output
Environment
Additional Context
No response