Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Dynamic default
incremental_strategy
for dbt-postgres and dbt-redsh…
…ift (#4652) resolves #4651 ### Previews - [dbt-postgres configs](https://docs-getdbt-com-git-dbeatty-dynamic-default-pos-c89442-dbt-labs.vercel.app/reference/resource-configs/postgres-configs#incremental-materialization-strategies) - [dbt-redshift configs](https://docs-getdbt-com-git-dbeatty-dynamic-default-pos-c89442-dbt-labs.vercel.app/reference/resource-configs/redshift-configs#incremental-materialization-strategies) ## What are you changing in this pull request and why? The default `incremental_strategy` for dbt-postgres and dbt-redshift is dynamic! It depends on [if `unique_key` is defined or not](#4633): - `delete_insert` when there is a unique_key defined and `append` otherwise All other adapters have a static default `incremental_strategy`. ## 🎩 <img width="400" alt="image" src="https://github.com/dbt-labs/docs.getdbt.com/assets/44704949/ba97b2cc-76e2-41d9-a8af-e1aeebb23a2d"> ## Checklist - [x] Review the [Content style guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md) so my content adheres to these guidelines.
- Loading branch information