v1.8.3

This release has the bug fixes and updates

• Fix #153
• Fix #136
• Upgrade Python driver to 2.4.1

v1.8.1

This is a minor release upgrade with the following updates:

• Added BLOB column type support in dbt contracts
• dbt show command's macro name is changed to oracle__get_limit_sql. This regressed 3 unit tests
• Fix signature of method create_schema
• Python driver upgraded to 2.3.0

v1.7.7

This release version has the following updates

• Fixes oracle adapter: Oracle error: ORA-12098: cannot comment on the materialized view

v1.8.0

This is a minor release upgrade with the following updates

• Decouple dbt-core and the base adapter and use a stable adapter interface i.e. dbt-adapters
• Addresses #138 and #149
• Fixes oracle adapter: Oracle error: ORA-12098: cannot comment on the materialized view
• database key in profile.yml is still optional for all but one of the dbt-oracle workflows. Without database name in profile.yml the generated catalog used for project documentation will be empty. For now, to circumvent the problem, dbt-oracle detects that database key is missing from profile.yml and issues a warning message to the user to add an entry in profile.yml for catalog generation. The warning message also shows the database name that dbt-oracle expects. That way users don't have to worry about "what" the database name is and "how" to get it.

v1.7.6

This release version has the following updates

• Upgraded oracledb driver to 2.2.1

• Fixed SQL generation for delete+insert incremental append strategy. Corresponding Slack thread - https://getdbt.slack.com/archives/C01PWH4TXLY/p1717577761754019

insertinto  schema.table (col1, col2, col3)
    (
       select col1, col2, col3
       from o$pt_test_xxxx100932446065
    )

"module": "dbt-1.7.15"
[0m10:09:38.080324 [info ] [Thread-2 (]: oracle adapter: Oracle error: ORA-00900: invalid SQL statement

v1.6.4

This release has the following updates:

• 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

Implements Deletes+Insert incremental strategy #128

Support for new partition_config in table and incremental materialization

partition_config={"clause": "PARTITION BY HASH(PROD_NAME) PARTITIONS 4"}

v1.7.5

This release includes the following updates:

• 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

v1.7.4

This release includes the following updates:

• Python oracledb driver upgraded to 2.1.2
• Fixes #139
• Removed cx_Oracle from 3rd party dependency list
• Addresses request to install dbt-oracle on ARM machines

v1.7.3

This release version has the following upgrades and bug fixes

• Added support for Python 3.12
• Implemented delete+insert incremental strategy - feature request #128
• Support for new partition_config in table and incremental materialization. This will add the partitioning clause in the CTAS DDL statement generated by dbt-oracle.

partition_config={"clause": "PARTITION BY HASH(PROD_NAME) PARTITIONS 4"}

• oracledb driver upgraded to 2.1.0
• minor readme updates

v1.6.3

This release version has the following upgrades and bug fixes

• Fix for Bug #130 : Quoting Identifier True and Persist docs
• Fix for Bug #129 : table materialization fails when another MV with the same name exists in database
• Fix for dbt contracts using CLOB datatype (e.g. Kafka messages)
• Python Driver upgraded to oracledb==2.0.1

Contributors: @amoghparab1805