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] Commented: (DERBY-4754) SQLClob.getObject() should always return a java.sql.Clob
Date Wed, 04 Aug 2010 13:33:16 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12895256#action_12895256
] 

Rick Hillegas commented on DERBY-4754:
--------------------------------------

Tests passed cleanly for me with this patch, except for a ping heisenbug in the network environment.

> 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
>         Attachments: derby-4754-01-aa-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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message