[
https://issues.apache.org/jira/browse/DERBY-4830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12917606#action_12917606
]
Benson Margulies commented on DERBY-4830:
-----------------------------------------
I have no objection to your analysis. It seems to be a very strange aspect of
the JDBC set, but there is stiff competition for the title of 'strangest aspect
of the JDBC API.' Thank you very much for explaining it to me.
> ResultSet.getCharacterStream returns closed stream for clob
> -----------------------------------------------------------
>
> Key: DERBY-4830
> URL: https://issues.apache.org/jira/browse/DERBY-4830
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.6.1.0
> Reporter: Benson Margulies
> Priority: Minor
> Attachments: derby-4830.tar.gz
>
>
> After selecting a clob, the following works:
> {code}
> rs.getClob(1).getCharacterStream()
> {code}
> However, simply calling
> {code}
> rs.getCharacterStream(1)
> {code}
> returns a closed StringReader.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
