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 (Closed) (JIRA)" <ji...@apache.org> on 2012/02/16 00:10:05 UTC
[jira] [Closed] (DERBY-4754) SQLClob.getObject() should always
return a java.sql.Clob
[ https://issues.apache.org/jira/browse/DERBY-4754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden closed DERBY-4754.
---------------------------------
Resolution: Fixed
> SQLClob.getObject() should always return a java.sql.Clob
> --------------------------------------------------------
>
> Key: DERBY-4754
> URL: https://issues.apache.org/jira/browse/DERBY-4754
> Project: Derby
> Issue Type: Bug
> Components: JDBC, SQL
> Affects Versions: 10.6.1.0
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Labels: derby_triage10_8
> Fix For: 10.7.1.1
>
> Attachments: derby-4066-02-ac-outputLOBs.diff, derby-4754-01-aa-harmonyLOBs.diff, derby-4754-01-ab-harmonyLOBs.diff
>
>
> Depending on what SQLClob wraps (a string, a stream, a java.sql.Clob), SQLClob.getObject() sometimes returns a string and other times returns a java.sql.Clob. In at least one spot, the compiler expects that SQLClob.getObject() will always return a java.sql.Clob. See the final cast compiled by SQLToJavaValueNode.generateJavaValue(). I believe that the compiler is correct and SQLClob.getObject() should behave predictably.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira