db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1811) Embedded ResultSet.getTimestamp on a TIME column returns a java.sql.Timestamp with a date portion that can be incorrect.
Date Wed, 11 Oct 2006 08:44:22 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1811?page=comments#action_12441379 ] 
            
Kristian Waagan commented on DERBY-1811:
----------------------------------------

Has all work been finsihed on this issue?
If so, please close it.
I was looking at this because we now see failures in the All suite for TimeHandlingTest under
DerbyNetClient.

> Embedded ResultSet.getTimestamp on a TIME column returns a java.sql.Timestamp with a
date portion that can be incorrect.
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1811
>                 URL: http://issues.apache.org/jira/browse/DERBY-1811
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC
>    Affects Versions: 10.1.3.1, 10.1.2.1, 10.1.1.0, 10.0.2.1, 10.0.2.0, 10.0.2.2, 10.1.3.2,
10.1.4.0, 10.2.1.6, 10.3.0.0
>            Reporter: Daniel John Debrunner
>         Assigned To: Daniel John Debrunner
>             Fix For: 10.3.0.0
>
>         Attachments: derby1811_diff.txt
>
>
> 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.

-- 
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

        

Mime
View raw message