[DERBY-4625] TIMESTAMP function doesn't accept nanoseconds

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.5.3.0
• Fix Version/s: 10.5.3.2, 10.6.2.4, 10.7.1.1
• Component/s: SQL
• Assignee: Nirmal Fernando
• Reporter: Knut Anders Hatlen
• Created: 21/Apr/10 10:57
• Updated: 30/Jun/11 09:21
• Resolved: 16/Feb/11 00:05

Description

The TIMESTAMP function fails if the string argument specifies the number of nanoseconds. It works if the argument is limited to microsecond resolution.

ij> values timestamp('2010-04-21 12:00:00.123456');
1
--------------------------
2010-04-21 12:00:00.123456

1 row selected
ij> values timestamp('2010-04-21 12:00:00.123456789');
ERROR 22008: '2010-04-21 12:00:00.123456789' is an invalid argument to the timestamp function.

Since Derby (and JDBC) supports nanosecond resolution, the TIMESTAMP function should also support it.

Issue Links

• is related to: DERBY-4614 JDBC metadata gives incorrect lengths for timestamps
• is required by: DERBY-4994 10.5 backport effort issue (2011)
• relates to: DERBY-4626 Timestamp truncated when converted to string with explicit calendar
• relates to: DERBY-2602 TIMESTAMP value is truncated when return to client