[DERBY-1811] Embedded ResultSet.getTimestamp on a TIME column returns a java.sql.Timestamp with a date portion that can be incorrect.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.0.2.0, 10.0.2.1, 10.0.2.2, 10.1.1.0, 10.1.2.1, 10.1.3.1, 10.1.3.2, 10.1.3.3, 10.2.1.6, 10.3.1.4
• Fix Version/s: 10.2.1.6, 10.2.2.0, 10.3.1.4
• Component/s: JDBC
• Assignee: Daniel John Debrunner
• Reporter: Daniel John Debrunner
• Created: 03/Sep/06 05:12
• Updated: 05/Jul/10 17:32
• Resolved: 23/May/07 01:14

Description

The date portion of the java.sql.Timestamp from a TIME column is intended to be the current date but instead can be any date value, based upon the last getXXX call that required a Java Calendar object.

Issue Links

• is related to: DERBY-889 with client getTimestamp on a TIME column will print the date 1900-01-01 instead of the current date