[
https://issues.apache.org/jira/browse/CALCITE-6315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17835042#comment-17835042
]
Norman Jordan commented on CALCITE-6315:
----------------------------------------
[~jerin_john] Thanks for letting me know about your work. It looks like some of
these will difficult to support with {*}SimpleDateFormat{*}. There is already
support for {*}FF1{*}, {*}FF2{*}, {*}FF4{*}, {*}FF5{*}, and {*}FF6{*}. Calcite
will produce different results for these than PostgreSQL.
Consider this timestamp *2022-06-03 12:15:48.678*
|| ||FF1||FF2||FF4||FF5||FF6||
|Calcite|678|678|0678|00678|000678|
|PostgreSQL|6|67|6780|67800|678000|
The Calcite result for *FF3* matches PostgreSQL.
There are some other formats such as *IYYY* that cannot be supported using
{*}SimpleDateFormat{*}.
> Support PostgreSQL TO_CHAR, TO_DATE, TO_TIMESTAMP
> -------------------------------------------------
>
> Key: CALCITE-6315
> URL: https://issues.apache.org/jira/browse/CALCITE-6315
> Project: Calcite
> Issue Type: Sub-task
> Reporter: James Duong
> Priority: Minor
> Labels: pull-request-available
>
> PostgreSQL supports different format strings than the version we have
> implemented.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
