[DERBY-889] with client getTimestamp on a TIME column will print the date 1900-01-01 instead of the current date

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.1.2.1, 10.1.3.1, 10.2.1.6
• Fix Version/s: 10.3.1.4
• Component/s: Network Client
• Assignee: Bryan Pendleton
• Reporter: Katherine Marsden
• Created: 29/Jan/06 16:31
• Updated: 03/Apr/13 12:56
• Resolved: 11/May/07 22:08

Description

On client getTimestamp on a TIME column will print date 1900-01-01 instead of the current date like the embedded driver.
To repro run the DERBY-877 repro without specifying a file.encoding

java TestEnc derbynetclient
[snip]
COLUMN 2:TM TIME
getString: 16:27:35
getTimeStamp: 1900-01-01 16:27:35.0
getTime: 16:27:35
getDate Exception SQLSTATE:null (EXPECTED)

With Embedded it prints the current date for getTimestamp
java TestEnc derby

COLUMN 2:TM TIME
getString: 16:27:35
getTimeStamp: 2006-01-28 16:27:35.0
getTime: 16:27:35
getDate Exception SQLSTATE:22005 (EXPECTED)

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-1816 Client's ResultSet.getTime() on a SQL TIMESTAMP column loses the sub-second resolution and always has a milli-second value of zero.
• relates to: DERBY-1811 Embedded ResultSet.getTimestamp on a TIME column returns a java.sql.Timestamp with a date portion that can be incorrect.
• relates to: DERBY-3519 junit regression test failure in testInertTime(org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest)junit.framework.AssertionFailedError: expected:<2> but was:<3>