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
implementation of delete+insert incremental strategy
Describe alternatives you've considered
using a pre hook on the model to delete the data or trying to implement the custom strategy myself, the first seems prone to error and the later convoluted
Who will this benefit?
dbt offers different strategies to make incremental models. the ones currently implemented are append and merge (as I understand). although they are not fit for all use cases. for example when reruns are desired and the table has no key
- Added support for Python 3.12
- oracledb driver upgraded to 2.1.0
- Added support for delete+insert incremental strategy addressing #128
- Added support for new config `partition_config`
- Upgrade oracledb driver to v2.2.0
- Fix Oracle error: ORA-14452: attempt to create, alter or drop an index on temporary table already in use while using constraints with Incremental materialization. Issue discussed and fix verified in this slack thread : https://getdbt.slack.com/archives/C01PWH4TXLY/p1712669363630279
- Feature request [Feature] implement delete+insert incremental strategy #128
- Support for new partition_config in table and incremental materialization
Describe the Feature
implementation of delete+insert incremental strategy
Describe alternatives you've considered
using a pre hook on the model to delete the data or trying to implement the custom strategy myself, the first seems prone to error and the later convoluted
Who will this benefit?
dbt offers different strategies to make incremental models. the ones currently implemented are append and merge (as I understand). although they are not fit for all use cases. for example when reruns are desired and the table has no key
Anything else?
https://docs.getdbt.com/docs/build/incremental-models#about-incremental_strategy
The text was updated successfully, but these errors were encountered: