[DERBY-2602] TIMESTAMP value is truncated when return to client

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.3.1.4
• Fix Version/s: 10.6.1.0
• Component/s: Network Client
• Urgency: Normal
• Issue & fix info: Repro attached
• Bug behavior facts: Deviation from standard, Embedded/Client difference, Wrong query result
• Assignee: Richard N. Hillegas
• Reporter: Katherine Marsden
• Created: 02/May/07 19:36
• Updated: 12/Jan/11 22:24
• Resolved: 13/Jul/10 01:36

Description

In ParameterMappingTest I see the following differences between embedded and client. Client is truncating the TIMESTAMP value. Look for this bug number in the test for reproduction.

case java.sql.Types.TIMESTAMP:
if (param == 2)
if (usingEmbedded())
assertEquals("2004-03-12 21:14:24.938222433", val.toString());
else
assertEquals("2004-03-12 21:14:24.938222", val.toString());
else if (param == 3)
if (usingEmbedded())
assertEquals("2004-04-12 04:25:26.462983731", val.toString());
else
assertEquals("2004-04-12 04:25:26.462983", val.toString());
break;

Issue Links

• is part of: DERBY-2034 Tracking of bugs that lead to incorrect results being stored or returned to the client
• is related to: DERBY-4614 JDBC metadata gives incorrect lengths for timestamps
• is related to: DERBY-4626 Timestamp truncated when converted to string with explicit calendar
• is related to: DERBY-4625 TIMESTAMP function doesn't accept nanoseconds
• is required by: DERBY-4728 10.5 backport effort tracking issue
• relates to: DERBY-1816 Client's ResultSet.getTime() on a SQL TIMESTAMP column loses the sub-second resolution and always has a milli-second value of zero.