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 "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2007/05/23 03:15:16 UTC
[jira] Reopened: (DERBY-1811) Embedded ResultSet.getTimestamp on a
TIME column returns a java.sql.Timestamp with a date portion that can be
incorrect.
[ https://issues.apache.org/jira/browse/DERBY-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren reopened DERBY-1811:
---------------------------------------
> Embedded ResultSet.getTimestamp on a TIME column returns a java.sql.Timestamp with a date portion that can be incorrect.
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1811
> URL: https://issues.apache.org/jira/browse/DERBY-1811
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 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.4.0, 10.2.1.6, 10.3.0.0
> Reporter: Daniel John Debrunner
> Assigned To: Daniel John Debrunner
> Fix For: 10.2.1.6, 10.2.2.0, 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.
-
You can reply to this email to add a comment to the issue online.