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 "Rick Hillegas (JIRA)" <ji...@apache.org> on 2010/07/23 18:10:51 UTC

[jira] Updated: (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 ]

Rick Hillegas updated DERBY-4754:
---------------------------------

    Affects Version/s: 10.6.1.0
          Component/s: SQL

> 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: SQL
>    Affects Versions: 10.6.1.0
>            Reporter: Rick Hillegas
>
> 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.
-
You can reply to this email to add a comment to the issue online.