You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kathey Marsden (JIRA)" <ji...@apache.org> on 2007/05/11 20:09:15 UTC
[jira] Resolved: (DERBY-889) with client getTimestamp on a TIME
column will print the date 1900-01-01 instead of the current date
[ https://issues.apache.org/jira/browse/DERBY-889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden resolved DERBY-889.
----------------------------------
Resolution: Fixed
Assignee: Bryan Pendleton (was: Kathey Marsden)
Committed Bryan's fix for this issue.
revision 537252.
> with client getTimestamp on a TIME column will print the date 1900-01-01 instead of the current date
> -----------------------------------------------------------------------------------------------------
>
> Key: DERBY-889
> URL: https://issues.apache.org/jira/browse/DERBY-889
> Project: Derby
> Issue Type: Bug
> Components: Network Client
> Affects Versions: 10.1.2.1, 10.1.3.1, 10.2.1.6
> Reporter: Kathey Marsden
> Assigned To: Bryan Pendleton
> Attachments: derby-889-updated-Aug-2006.diff, derby-889-withCalTests.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.
-
You can reply to this email to add a comment to the issue online.