[jira] [Commented] (CALCITE-1690) Calcite timestamp literals cannot express precision above millisecond, TIMESTAMP(3)

2017-05-23 Thread Julian Hyde (JIRA)
[ https://issues.apache.org/jira/browse/CALCITE-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16020703#comment-16020703 ] Julian Hyde commented on CALCITE-1690: -- Fixed in Avatica in

[jira] [Commented] (CALCITE-1690) Calcite timestamp literals cannot express precision above millisecond, TIMESTAMP(3)

2017-05-23 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/CALCITE-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16020701#comment-16020701 ] ASF GitHub Bot commented on CALCITE-1690: - Github user asfgit closed the pull request at:

[jira] [Commented] (CALCITE-1690) Calcite timestamp literals cannot express precision above millisecond, TIMESTAMP(3)

2017-05-12 Thread Ashutosh Chauhan (JIRA)
[ https://issues.apache.org/jira/browse/CALCITE-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16008755#comment-16008755 ] Ashutosh Chauhan commented on CALCITE-1690: --- May be its time to drop support for jdk7. jdk8 is

[jira] [Commented] (CALCITE-1690) Calcite timestamp literals cannot express precision above millisecond, TIMESTAMP(3)

2017-05-03 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/CALCITE-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15995892#comment-15995892 ] ASF GitHub Bot commented on CALCITE-1690: - GitHub user julianhyde opened a pull request:

[jira] [Commented] (CALCITE-1690) Calcite timestamp literals cannot express precision above millisecond, TIMESTAMP(3)

2017-05-03 Thread Julian Hyde (JIRA)
[ https://issues.apache.org/jira/browse/CALCITE-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15995879#comment-15995879 ] Julian Hyde commented on CALCITE-1690: -- Here's how to create a high-precision timestamp literal:

[jira] [Commented] (CALCITE-1690) Calcite timestamp literals cannot express precision above millisecond, TIMESTAMP(3)

2017-04-28 Thread Julian Hyde (JIRA)
[ https://issues.apache.org/jira/browse/CALCITE-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15989675#comment-15989675 ] Julian Hyde commented on CALCITE-1690: -- Turns out that Joda-Time, while similar to java.time,

[jira] [Commented] (CALCITE-1690) Calcite timestamp literals cannot express precision above millisecond, TIMESTAMP(3)

2017-04-27 Thread Julian Hyde (JIRA)
[ https://issues.apache.org/jira/browse/CALCITE-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15987379#comment-15987379 ] Julian Hyde commented on CALCITE-1690: -- The SQL standard puts no upper bound on precision. In

[jira] [Commented] (CALCITE-1690) Calcite timestamp literals cannot express precision above millisecond, TIMESTAMP(3)

2017-04-27 Thread Julian Hyde (JIRA)
[ https://issues.apache.org/jira/browse/CALCITE-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15987366#comment-15987366 ] Julian Hyde commented on CALCITE-1690: -- Calcite already uses Joda-Time, and its

[jira] [Commented] (CALCITE-1690) Calcite timestamp literals cannot express precision above millisecond, TIMESTAMP(3)

2017-03-13 Thread Remus Rusanu (JIRA)
[ https://issues.apache.org/jira/browse/CALCITE-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15907854#comment-15907854 ] Remus Rusanu commented on CALCITE-1690: --- Any opinion on how to address this? Supporting ANSI