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

Enrico Olivelli updated CALCITE-2406:
-------------------------------------
    Description: 
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/Validator.

 

It is not a requirement that the Validator converts the literal directly, a 
string will be fine, so that downstream the string will be parsed according to 
the Database/User/Session settings

 

 

 

  was:
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

 

 

 

 


> SqlValidator: 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/Validator.
>  
> It is not a requirement that the Validator converts the literal directly, a 
> string will be fine, so that downstream the string will be parsed according 
> to the Database/User/Session settings
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to