julianhyde commented on PR #2973:
URL: https://github.com/apache/calcite/pull/2973#issuecomment-1355981493
@mkou, In `SqlLibraryOperators`, the `TIMESTAMP` function should return a
Calcite `TIMESTAMP`, `DATE` will return `DATE`, and there is no `DATETIME`
function.
Elsewhere (or in
julianhyde commented on PR #2973:
URL: https://github.com/apache/calcite/pull/2973#issuecomment-1322750893
The precision issue really is orthogonal, so at best it muddies the waters.
See https://issues.apache.org/jira/browse/CALCITE-5266.
--
This is an automated message from the Apache
julianhyde commented on PR #2973:
URL: https://github.com/apache/calcite/pull/2973#issuecomment-1322748744
Let's move design discussions to the Jira case.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above
julianhyde commented on PR #2973:
URL: https://github.com/apache/calcite/pull/2973#issuecomment-1322709533
No, BigQuery, a timestamp is represented internally as an offset in
microseconds since epoch *UTC*.
The "UTC" is a crucial difference.
Sure, they're both a bunch of bits.
julianhyde commented on PR #2973:
URL: https://github.com/apache/calcite/pull/2973#issuecomment-1320951570
BQ `DATETIME` = Calcite `TIMESTAMP`
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the
