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] Updated: (DERBY-4531) Client setCharacterStream closes its Reader argument stream in finalizer
Date Mon, 01 Feb 2010 21:56:19 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dag H. Wanvik updated DERBY-4531:
---------------------------------

    Bug behavior facts: [Embedded/Client difference, Regression]  (was: [Embedded/Client difference])

This behavior was introduced in 10.2 with svn 414562, so marking
as regression until somebody convinces me this is not a bug ;-)

> 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: 10.2.1.6, 10.2.2.0, 10.3.1.4, 10.3.2.1, 10.3.3.0, 10.4.1.3, 10.4.2.0,
10.5.1.1, 10.5.2.0, 10.5.3.0
>            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.


Mime
View raw message