Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <20660223.178941281012675977.JavaMail.jira@thor>
Date: Thu, 5 Aug 2010 08:51:15 -0400 (EDT)
From: "Rick Hillegas (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-4754) SQLClob.getObject() should always
 return a java.sql.Clob
In-Reply-To: <15805729.546681279901450581.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

Tests passed cleanly for me except for the network ping problem. Committed second rev of the patch at subversion revision 982585.

> 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, 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.
-
You can reply to this email to add a comment to the issue online.