[ https://issues.apache.org/jira/browse/CALCITE-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16495869#comment-16495869 ]
James Duong commented on CALCITE-2339: -------------------------------------- The other downside I see: If someone used TIMESTAMPADD(ts, integer_column, DAY), we'd have to transform this to ts + integer_column * Interval '1' DAY, then transform it back to TIMESTAMPADD(ts, integer_column * 1, DAY) or if the interval's a non-literal: TIMESTAMPADD(ts, integer_column * cast(interval_expression as integer), DAY) > JDBC adapter should transform timestamp arithmetic for target database > ----------------------------------------------------------------------- > > Key: CALCITE-2339 > URL: https://issues.apache.org/jira/browse/CALCITE-2339 > Project: Calcite > Issue Type: Bug > Reporter: Julian Hyde > Assignee: Julian Hyde > Priority: Major > Attachments: Datetime Addition - Calcite.pdf > > > JDBC adapter should transform timestamp arithmetic for target database. > There are two ways in Calcite to add intervals to timestamps: the > TIMESTAMP_ADD function and the "<timestamp> + <interval>" operator. > The attached document (authored by James Doung) describes their pros and cons. -- This message was sent by Atlassian JIRA (v7.6.3#76005)