Fix: Change DatabaseException to DbtDatabaseError #205
+2
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Describe your changes
Since dbt-code 1.4.0 and above, the exception DatabaseException changed to DbtDatabaseError.
This leads to errors like
module dbt.exceptions has no attribute DatabaseException
when an actual Database Error happens.dbt-core source code > 1.7.0: https://github.com/dbt-labs/dbt-core/blob/v1.7.0/core/dbt/exceptions.py#L187
dbt-core source code > 1.3.7: https://github.com/dbt-labs/dbt-core/blob/v1.3.7/core/dbt/exceptions.py#L198
Internal Jira ticket number or external issue link
Testing procedure/screenshots(if appropriate):
Checklist before requesting a review