db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (DERBY-4754) SQLClob.getObject() should always return a java.sql.Clob
Date Wed, 06 Apr 2011 19:02:05 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rick Hillegas closed DERBY-4754.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 10.7.1.1

It appears to me that this bug has been 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
>              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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message