-
Notifications
You must be signed in to change notification settings - Fork 12
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
[Feature] dbt unit tests with postgres hstore #150
Labels
enhancement
New feature or request
unit tests
Issues related to built-in dbt unit testing functionality
Comments
dbeatty10
added
the
unit tests
Issues related to built-in dbt unit testing functionality
label
Sep 12, 2024
amychen1776
added
enhancement
New feature or request
and removed
bug
Something isn't working
triage
labels
Sep 24, 2024
amychen1776
changed the title
[Bug] dbt unit tests with postgres hstore
[Feature] dbt unit tests with postgres hstore
Sep 24, 2024
Hi @vincentclaes , thank you for opening this up! It seems like at the moment, we only support data types that:
So we are going to do two things related to this issue:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
New feature or request
unit tests
Issues related to built-in dbt unit testing functionality
Is this a new bug in dbt-core?
Current Behavior
Whenever my source table has a postgres hstore column type, the unittests will fail with a message like
It has either USER or USER-DEFINED in it and i figured out it always points to an hstore column.
Expected Behavior
That my tests would run without an issue.
Definitely if you do not specify the column in your tests.
Or is there a way to mock the input table so we can omit the hstore column?
Steps To Reproduce
Relevant log output
Environment
Which database adapter are you using with dbt?
postgres
Additional Context
dbt unit test:
dbt model
it even fails with the same message if I simplify to
The text was updated successfully, but these errors were encountered: