You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What part(s) of the page would you like to see updated?
From time-to-time, we get a question like this:
I'm using the FOO data type with BAR database, and I'm trying to add a model contract and/or unit tests. How come it isn't working?
Here's the super-specific nerd answer 🤓:
We support whichever data types meet these two criteria:
the data type name naturally falls out of an information_schema.columns query (or equivalent), and
cast(null as DATA_TYPE_NAME) works
For all the standard types in Postgres (int, varchar, date, etc, etc), both of the following hold. But it doesn't for the more exotic types (geometry, money, hstore, etc).
From what I can tell, we can actually overcome both in many scenarios. But it requires time and effort that could be difficult to prioritize.
But sometimes we are able to prioritize it. Like geography and geometry in Snowflake [1, 2, 3].
Additional information
No response
The text was updated successfully, but these errors were encountered:
Contributions
Link to the page on docs.getdbt.com requiring updates
Maybe one of these places? 🤷
What part(s) of the page would you like to see updated?
From time-to-time, we get a question like this:
Here's the super-specific nerd answer 🤓:
We support whichever data types meet these two criteria:
information_schema.columns
query (or equivalent), andcast(null as DATA_TYPE_NAME)
worksFor all the standard types in Postgres (
int
,varchar
,date
, etc, etc), both of the following hold. But it doesn't for the more exotic types (geometry
,money
,hstore
, etc).From what I can tell, we can actually overcome both in many scenarios. But it requires time and effort that could be difficult to prioritize.
But sometimes we are able to prioritize it. Like
geography
andgeometry
in Snowflake [1, 2, 3].Additional information
No response
The text was updated successfully, but these errors were encountered: