[
https://issues.apache.org/jira/browse/DERBY-4531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12828129#action_12828129
]
Dag H. Wanvik commented on DERBY-4531:
--------------------------------------
The client driver does not similarly close an InputStream given as as argument
to setBinaryStream.
> 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
> 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 be read to the number
> of chaaracters required or to EOF, whatever happens first.
> 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.
