You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "Mihai Budiu (Jira)" <ji...@apache.org> on 2024/03/15 02:36:00 UTC

[jira] [Resolved] (CALCITE-6138) Parser does not accept TIMESTAMP WITH TIME ZONE as a data type

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

Mihai Budiu resolved CALCITE-6138.
----------------------------------
    Resolution: Fixed

> Parser does not accept TIMESTAMP WITH TIME ZONE as a data type
> --------------------------------------------------------------
>
>                 Key: CALCITE-6138
>                 URL: https://issues.apache.org/jira/browse/CALCITE-6138
>             Project: Calcite
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.36.0
>            Reporter: Mihai Budiu
>            Assignee: Mihai Budiu
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 1.37.0
>
>
> The current SQL grammar accepts either TIMESTAMP WITHOUT TIME ZONE or TIMESTAMP WITH LOCAL TIME ZONE. It does not accept the version without LOCAL: TIMESTAMP WITH TIME ZONE. This is a legal type in other SQL dialects, and it appears in the SQL 92 standard.
> The Calcite documentation also lists the rejected type as a legal scalar type: [https://calcite.apache.org/docs/reference.html#scalar-types]
> So there is a bug: either the compiler is wrong, or the documentation is wrong. The main question is "which one?"



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