[DERBY-4626] Timestamp truncated when converted to string with explicit calendar

• Type: Bug
• Status: Closed
• Priority: Major
• 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
• Bug behavior facts: Wrong query result
• Assignee: Nirmal Fernando
• Reporter: Knut Anders Hatlen
• Created: 21/Apr/10 11:16
• Updated: 30/Jun/11 09:21
• Resolved: 16/Feb/11 21:20

Description

When setting the value of a VARCHAR parameter with setTimestamp() the timestamp is truncated to microsecond resolution if a calendar is specified. Nanosecond resolution is preserved when a calendar is not specified. These two methods should behave the same way. Since Derby supports nanosecond resolution, the timestamps should not be truncated.

Issue Links

• is related to: DERBY-4614 JDBC metadata gives incorrect lengths for timestamps
• is related to: DERBY-4625 TIMESTAMP function doesn't accept nanoseconds
• is required by: DERBY-4994 10.5 backport effort issue (2011)
• relates to: DERBY-2602 TIMESTAMP value is truncated when return to client