You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Julian Hyde (JIRA)" <ji...@apache.org> on 2018/11/02 02:20:00 UTC
[jira] [Commented] (CALCITE-2406) In Babel parser: allow to use raw
string literals for timestamps as in MySQL
[ https://issues.apache.org/jira/browse/CALCITE-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16672501#comment-16672501 ]
Julian Hyde commented on CALCITE-2406:
--------------------------------------
This is an issue with the validator rather than the parser. Babel would not be the place to fix it.
> In Babel parser: allow to use raw string literals for timestamps as in MySQL
> ----------------------------------------------------------------------------
>
> Key: CALCITE-2406
> URL: https://issues.apache.org/jira/browse/CALCITE-2406
> Project: Calcite
> Issue Type: New Feature
> Components: babel
> Affects Versions: 1.17.0
> Reporter: Enrico Olivelli
> Assignee: Julian Hyde
> Priority: Major
>
> I have some case of incompatibility between MySQL (actually on HerdDB which is a replacement for MySQL) and Calcite around timestamp syntax.
> In MySQL it is legal to write timestamp literals in this form:
> INSERT INTO table(tscolum) values('2018-12-22 22:33:00.333')
> This is currently not possible for standard Calcite SQL Parser
>
>
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)