-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CT-408] [Feature] Database Agnostic error handling #4926
Comments
@McKnight-42 The error message we're catching here is specific to the test added in #4858, and it's actually handled in a database-agnostic way there. We'll find out when we convert the test cases to use the new I think this can be closed, since the main work is already reflected in #4882 |
Is there an existing feature request for this?
Describe the Feature
Per #4858 (comment) the way we are catching database errors needs to be handled in a way that leverages each databases level of concern for the error or to catch them, and turn them into dbt specific errors and run those against tests
Describe alternatives you've considered
currently catching and lowering error to be read out same way across databases.
Who will this benefit?
potential for all uses to benefit as errors could be written very clearly across all databases.
Are you interested in contributing this feature?
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: