-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support float
arguments to to_timestamp
function
#7868
Labels
Comments
This was referenced Oct 19, 2023
I'll work on this |
Is this still up for grab? |
I'm still working on this; it's been a bit more involved than I expected. Is this blocking other issues? |
No blocking issues as of now, rather this is one of the missing pieces for timestamp. |
23 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem or challenge?
In #7844 we are (about to) change
to_timestamp
to be aligned with postgres by taking seconds instead of milliseconds.To fully align with postgres, we should also add support
double
(Float64
) arguments as wellThe postgres documentation for
to_timestamp
is hereDescribe the solution you'd like
I would like the
to_timestamp
function to also support Float64 point arguments:For example, (not the
1.1
at the end of the timestamp)willy=# select to_timestamp(1.1); to_timestamp -------------------------- 1970-01-01 08:00:01.1+08
Describe alternatives you've considered
No response
Additional context
Note the string / two argument version of
to_timestamp
is covered by #5398The text was updated successfully, but these errors were encountered: