v1.9.4

This release includes the following updates and fixes

• dbt-core requirement upgraded to 1.10 - Fixes #186
• Python driver requirement upgraded to v3.3.0
• Oracle Column Metadata for VARCHAR datatype now includes size and unit e.g. VARCHAR32(5, char). Fixes #190

v1.9.3

This release includes the following updates:

• Fixed bug #179 for dbt snapshots

• Python driver upgraded to 3.2.0

v1.9.2

This release includes the following updates:

• Support for direct path inserts in incremental materialization fixing #174
• Fix bug for snapshot config snapshot_meta_column_names
• Python driver upgraded to 3.1.1

v1.9.1

This release includes the following updates:

• Python driver version upgraded to 3.1.0

• New snapshot improvements introduced in 1.9. This fixes bug #165

• Macro oracle__snapshot_hash_arguments uses a much stronger hash function (SHA-256) to avoid hash collisions in snapshots. Fixes #154

• HTTP proxy environment variables are ignored. To connect to the database via https proxy, please include the proxy attributes in dbt profile. Fixes #168

outputs:
      dev:
         type: oracle
         user: "{{ env_var('DBT_ORACLE_USER') }}"
         pass: "{{ env_var('DBT_ORACLE_PASSWORD') }}"
         ..
         https_proxy: "www-proxy.com"
         https_proxy_port: 80

v1.9.0

This release has the following fixes and updates

• dbt-core upgraded to 1.9.0
• Support for external auth. Fixes #157

v1.8.4

This release has the following bug fixes and updates

• Fixes #158
• Upgrades driver to 2.5.1
• Dropped support for Python 3.8
• Use timestamp(9) in dbt snapshots for dbt_valid_to column

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.