[CALCITE-2281] TIMESTAMPADD(MICROSECOND, ...) returns incorrect results

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.17.0
• Component/s: core
• Assignee: Julian Hyde
• Reporter: Sudheesh Katkam
• Created: 26/Apr/18 00:25
• Updated: 20/Jul/18 08:18
• Resolved: 29/Jun/18 18:46

Description

Add this test to SqlOperatorBaseTest#testTimestampAdd :

tester.checkScalar(
    "timestampadd(MICROSECOND, 2, timestamp '2016-02-24 12:42:25.000000')",
    "2016-02-24 12:42:25.000002",
    "TIMESTAMP(6) NOT NULL");

SqlTimestampAddFunction has incorrect precision for MILLISECOND and MICROSECOND. Note that the parser does not allow for MILLISECOND as a time unit.

Issue Links

• is related to: CALCITE-2299 TIMESTAMPADD(SQL_TSI_FRAC_SECOND) should be nanoseconds not microseconds