db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4531) Client setCharacterStream closes its Reader argument stream in finalizer
Date Mon, 01 Feb 2010 22:06:18 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12828294#action_12828294

Dag H. Wanvik commented on DERBY-4531:

Derby will throw if the stream does not hold the exact amount of data specified in setCharacterStream,
so one might argue that keeping the stream open doesn't accomplish much. Still, I think that
since the API does not prescribe closing the stream, a driver should refrain from doing it.

> Client setCharacterStream closes its Reader argument stream in finalizer
> ------------------------------------------------------------------------
>                 Key: DERBY-4531
>                 URL: https://issues.apache.org/jira/browse/DERBY-4531
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Client
>    Affects Versions:,,,,,,,,,
>            Reporter: Dag H. Wanvik
>            Priority: Minor
> The javadoc for PreparedStatement.setCharacterStream does not specify that the stream
passed in will be closed, only that it will read to the number of characters specified.
> For the embedded driver, the stream is not closed after execution; the client driver,
however, will close the stream when the internal stream object EncodedInputStream is garbage
collected, which can happen any time after the statement has been executed.
> I am not sure this a bug vs. the JDBC specification, but it would be nice to harmonize
client and embedded behavior on this.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message