Feat: add dtntz date macro variant #4838
Merged
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.
Addresses the issue discussed in this Slack thread: https://tobiko-data.slack.com/archives/C044BRE5W4S/p1749739413928599.
The
_dt
date macro variables always inject a time zone in the resultingdatetime
object, even if it'sUTC
. This is problematic in certain cases, e.g., when these values are compared to a zone-unaware timestamps. For instance, Redshift isn't clever enough when comparing zone-aware and unaware timestamps, leading to full scans instead of pruning.The only alternative that exists today to work around this issue is to have string versions of these date values and cast them, which isn't a great experience. This PR covers this feature gap.