[ https://issues.apache.org/jira/browse/CALCITE-2699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16697130#comment-16697130 ]
xuqianjin commented on CALCITE-2699: ------------------------------------ [~kgyrtkirk] Your conclusion is correct. Null is due to my mysql connection to the client.I've changed it > The bug of timestampadd handles time > ------------------------------------- > > Key: CALCITE-2699 > URL: https://issues.apache.org/jira/browse/CALCITE-2699 > Project: Calcite > Issue Type: Bug > Components: core > Affects Versions: 1.17.0, 1.18.0 > Reporter: xuqianjin > Assignee: Julian Hyde > Priority: Major > > Two errors occur when {{timestampadd(MINUTE, 1, time '01:00:00')}} is > executed: > # The return result can only be of {{TimeStamp}} type and is expected to be > of {{Time}} type > # The return value is {{1970-01-01 01:01:00}}, and the expectation is > {{01:01:00}} > # Compared with {{mysql}} database, I think it should meet the following > conditions: > ||expression||Expect the result|| > |timestampadd(MINUTE, -1, time '00:00:00')|NULL| > |timestampadd(MINUTE, 1, time '00:00:00')|00:01:00| > |timestampadd(MINUTE, 1, time '23:59:59')|00:00:59| > |timestampadd(SECOND, 1, time '23:59:59')|00:00:00| > |timestampadd(HOUR, 1, time '23:59:59')|00:59:59| -- This message was sent by Atlassian JIRA (v7.6.3#76005)