[ http://issues.apache.org/jira/browse/DERBY-889?page=comments#action_12432312 ] Daniel John Debrunner commented on DERBY-889: ---------------------------------------------
I think this is in-line with the current documented handling of the DATE->java.sql.Date, TIME->java.sql.Time and TIMESTAMP->java.sql.Timestamp in http://db.apache.org/derby/papers/JDBCImplementation.html#Date+Handling That document could be updated with for conversions of DATE to java.sql.Timestamp and TIME to java.sql.Timestamp > with client getTimestamp on a TIME column will print the date 1900-01-01 > instead of the current date > ----------------------------------------------------------------------------------------------------- > > Key: DERBY-889 > URL: http://issues.apache.org/jira/browse/DERBY-889 > Project: Derby > Issue Type: Bug > Components: Network Client > Affects Versions: 10.1.2.1, 10.1.2.2, 10.2.1.0, 10.1.3.0 > Reporter: Kathey Marsden > Assigned To: Bryan Pendleton > Attachments: derby-889-updated-Aug-2006.diff, derby-889.diff > > > 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) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
