Support coercing utf8
to interval
and timestamp
(including arguments to date_bin
)
#5117
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.
Draft as itWhich issue does this PR close?
Closes #4853
Rationale for this change
Rationale:
date_bin
with a string value does not work and gives a hard to understand message:What changes are included in this PR?
Utf8
constants can be automatically coerced into Intervals (same as today)Utf8
can be automatically coerced into TimestampsAre these changes tested?
Yes
Are there any user-facing changes?
Yes, strings are now automatically coerced into
Timetamp
s andIntervals
Note this behavior is consistent with Postgres: