Josh Wills
Josh Wills
@actuary87 hello! I am back in the US and want to get this timestamp stuff working this week
So interesting; I cannot for the life of me figure out what is making it unhappy with the timestamp values
Ah, great question. So many of the `pg_catalog` tables do exist; DuckDB has implementations for many of them here: https://github.com/duckdb/duckdb/blob/master/src/catalog/default/default_views.cpp The problem, of course, is that it doesn't support _all_...
yeah exactly, it wasn't too-too hard to write them: https://github.com/jwills/buenavista/blob/main/buenavista/examples/duckdb_http.py
Hey @geoHeil for the `duckdb_http` stuff you want to use the presto connector in datagrip
Ack, how did I miss this issue-- sorry about that, my mind has (clearly!) been elsewhere. ADBC is a client-side protocol, so I don't quite follow what you want BV...
Mmm I think there are a few problems here. 1) You definitely need to add `"` around the `{{ dataset }}` variable in the model SQL; dbt doesn't do that...
@DanyC97 that does make sense, but I don't see how DuckDB would help with that problem since I assume you need to use BigQuery to read that data; dbt-duckdb doesn't...
yeah I'm surprised this didn't break on the regular unit tests-- like, does this not work anymore and I missed it? https://github.com/dbt-labs/dbt-adapters/blob/main/dbt-tests-adapter/dbt/tests/adapter/utils/fixture_dateadd.py
My concern here is what happens if I pass in a `TIMESTAMP` instead of a string or a `DATE`? Or a string that should be cast as a `TIMESTAMP` instead?