db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4830) ResultSet.getCharacterStream returns closed stream for clob
Date Mon, 04 Oct 2010 09:57:33 GMT

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

Kristian Waagan commented on DERBY-4830:
----------------------------------------

Do you have any more details on this?
Is it happening with the embedded driver, the client driver, or both?
Can you easily write some running code that demonstrates the problem?

I'm positive rs.getCharacterStream(1) works in the general case, it would be nice to identify
the circumstances that trigger the problem.


Thanks,

> 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
>
> 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.


Mime
View raw message