Improved support for dbt_date and dbt_metrics #18
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
dbt_date
needs to know how to convert a time zone. trino does that{{ column }} at time zone '{{ target_tz }}'
dbt_metrics
uses somedateadd
functionality that looks like this in trino:date_add('day', -5, calendar.date_day)
I did not run any tests except that I succeeded in generating some metrics and using some date functions.
To make this work, one should adapt their
dbt_project.yml
to includeWe should also probably modify this repo's readme