You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "TJ Banghart (Jira)" <ji...@apache.org> on 2023/02/28 23:22:00 UTC

[jira] [Assigned] (CALCITE-5290) Add DATE_TRUNC function consistent with Postgres

     [ https://issues.apache.org/jira/browse/CALCITE-5290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

TJ Banghart reassigned CALCITE-5290:
------------------------------------

    Assignee: TJ Banghart

> Add DATE_TRUNC function consistent with Postgres
> ------------------------------------------------
>
>                 Key: CALCITE-5290
>                 URL: https://issues.apache.org/jira/browse/CALCITE-5290
>             Project: Calcite
>          Issue Type: Bug
>            Reporter: Julian Hyde
>            Assignee: TJ Banghart
>            Priority: Major
>
> Add {{DATE_TRUNC}} function consistent with Postgres. Per the [specification|https://www.postgresql.org/docs/current/functions-datetime.html#FUNCTIONS-DATETIME-TRUNC], syntax is as follows:
> {code}
> DATE_TRUNC(<string>, <timestamp | date | time>)
> {code}
> It is a different (and more complex) specification than BigQuery's DATE_TRUNC (see CALCITE-5180), which has the following syntax:
> {code}
> DATE_TRUNC(<date>, <interval>)
> {code}
> Postgres DATE_TRUNC would be implemented after CALCITE-5155 and would allow user-defined time frames in the {{field}} argument.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)