Analyze whether the migration of dbt_utils `current_timestamp` macros in dbt 1.3.0 affects dbt-trino
findinpath opened this issue · 1 comments
findinpath commented
Describe the feature
https://github.com/dbt-labs/dbt-core/releases/tag/v1.3.0
Migrate dbt-utils current_timestamp macros into core + adapters (dbt-labs/dbt-core#5521, dbt-labs/dbt-core#5838)
Describe alternatives you've considered
No response
Who will benefit?
No response
Are you willing to submit PR?
- Yes I am willing to submit a PR!
mdesmet commented
See following note in the dbt core PR.
As we consistently used current_timestamp we are not affected by this issue.
/* {#
DEPRECATED: DO NOT USE IN NEW PROJECTS
This is ONLY to handle the fact that Snowflake + Postgres had functionally
different implementations of {{ dbt.current_timestamp }} + {{ dbt_utils.current_timestamp }}
If you had a project or package that called {{ dbt_utils.current_timestamp() }}, you should
continue to use this macro to guarantee identical behavior on those two databases.
#} */