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

Posted to issues@calcite.apache.org by "Jesus Camacho Rodriguez (JIRA)" <ji...@apache.org> on 2019/07/12 22:18:00 UTC

[jira] [Resolved] (CALCITE-3189) Multiple fixes for Oracle SQL dialect

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

Jesus Camacho Rodriguez resolved CALCITE-3189.
----------------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.21.0

Fixed in [0732283cab7894ffdce6a22ebe5d31b28d389a4d|https://github.com/apache/calcite/commit/0732283cab7894ffdce6a22ebe5d31b28d389a4d].

> Multiple fixes for Oracle SQL dialect
> -------------------------------------
>
>                 Key: CALCITE-3189
>                 URL: https://issues.apache.org/jira/browse/CALCITE-3189
>             Project: Calcite
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.20.0
>            Reporter: Jesus Camacho Rodriguez
>            Assignee: Jesus Camacho Rodriguez
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.21.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Among others, it includes i) SQL translation support for specific types (e.g. {{SMALLINT}} --> {{NUMBER(5)}}), ii) limiting max length of {{VARCHAR}} type (by default 4000), iii) creating datetime literals correctly, and iv) method to infer whether a given data type is supported or not.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)