[
https://issues.apache.org/jira/browse/CALCITE-6358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17836261#comment-17836261
]
Julian Hyde commented on CALCITE-6358:
--------------------------------------
In Calcite, the set of format elements is tied to particular functions, not set
system-wide. You could, say, have a TO_CHAR function that uses Postgres and a
TO_TIMESTAMP function that uses BigQuery elements.
So, my question is: which functions do you intend to test as part of this case?
> Support all PostgreSQL 14 date/time patterns
> --------------------------------------------
>
> Key: CALCITE-6358
> URL: https://issues.apache.org/jira/browse/CALCITE-6358
> Project: Calcite
> Issue Type: Sub-task
> Reporter: Norman Jordan
> Priority: Minor
>
> Many of the date/time format patterns supported by PostgreSQL 14 are not
> supported in Calcite.
> * HH
> * US
> * SSSS
> * SSSSS
> * AM
> * A.M.
> * am
> * a.m.
> * PM
> * P.M.
> * pm
> * p.m.
> * Y,YYY
> * YYY
> * Y
> * IYYY
> * IYY
> * IY
> * I
> * BC
> * B.C.
> * bc
> * b.c.
> * AD
> * A.D.
> * ad
> * a.d.
> * MONTH
> * month
> * MON
> * mon
> * DAY
> * day
> * Dy
> * dy
> * IDDD
> * ID
> * TZH
> * TZM
> * OF
> There are also template pattern modifiers that need to be supported.
> * FM (prefix)
> * TH (suffix)
> * th (suffix)
> * FX (prefix)
> * TM (prefix)
> Some format patterns in Calcite behave differently from PostgreSQL 14.
> * FF1
> * FF2
> * FF4
> * FF5
> * FF6
> Also verify that the other existing format strings produce results that match
> PostgreSQL 14.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
