Open james-johnston-thumbtack opened 10 months ago
This is a bug in the dbt-postgres
adapter (which this adapter shims). We fixed it a while back in our own adapter (dbt-materialize
), but I just opened a PR to also fix it upstream: https://github.com/dbt-labs/dbt-postgres/pull/98.
@james-johnston-thumbtack which dbt driver are you using for RW? dbt-risingwave or dbt-postgres?
@neverchanje I was testing with the dbt-risingwave adapter.
The dbt-risingwave
adapter inherits from dbt-postgres
. What I meant is that once this is fixed in dbt-postgres
, it'll just work for this adapter too.
RisingWave supports
COMMENT ON
syntax, as documented here: https://docs.risingwave.com/docs/current/sql-comment-on/However, if I set the
persist_docs
config like this, as documented at https://docs.getdbt.com/reference/resource-configs/persist_docs:Then dbt will fail with an error like this:
Obviously this is invalid SQL.... I'm guessing the feature is not supported yet.
Definitely a low-priority nice-to-have for me, since I'll also be looking at using the dbt documentation generator. But in the future it would be nice if anyone directly browsing the database can have these descriptions close at hand.