[ http://issues.apache.org/jira/browse/DERBY-1811?page=all ]
Daniel John Debrunner updated DERBY-1811:
-----------------------------------------
Attachment: derby1811_diff.txt
Patch that ensures calendars are cleared before use in the SQL datatypes and
that conversion of a SQL TIME to a JDBC java.sql.Timestamp makes the date
component is set to the current date (not the SQL CURRENT DATE).
This passes all the tests but not ready for commit, need some more testing to
double check it does not effect any SQL casts of TIME TO TIMESTAMP which use
the SQL CURRENT DATE as the date portion.
> 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.0.2.0, 10.0.2.1, 10.0.2.2, 10.1.1.0, 10.2.1.0,
> 10.1.2.1, 10.1.3.0, 10.3.0.0, 10.1.4.0, 10.1.3.1, 10.1.3.2
> Reporter: Daniel John Debrunner
> Assigned To: Daniel John Debrunner
> 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
