[
https://issues.apache.org/jira/browse/DERBY-4521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086531#comment-13086531
]
Kathey Marsden commented on DERBY-4521:
---------------------------------------
Labeled derby_backport_reject_10_8. Since it is a behavior change prohibiting
an operation, probably not suitable for a maintenance release.
> Stream passed out to user does not heed close, allowing reads after next
> ResultSet#getXXX
> -----------------------------------------------------------------------------------------
>
> Key: DERBY-4521
> URL: https://issues.apache.org/jira/browse/DERBY-4521
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.1.2.1, 10.1.3.1,
> 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, 10.6.1.0, 10.6.2.1, 10.7.1.1
> Reporter: Dag H. Wanvik
> Priority: Minor
> Labels: derby_backport_reject_10_8, derby_triage10_8
> Fix For: 10.9.0.0
>
> Attachments: repro.diff
>
>
> This was discovered investigating DERBY-4477 using the repro for DERBY-3646,
> which erroneously
> tries to keep two streams passed out via REsultSet#getBinaryStream open at
> the same time. This is prohibited by JDBC [1],
> but Derby allows it for non-materialized streams because the close call on
> the passed out stream (performed by EmbedResultSet#closeCurrentStream at the
> time of the next getXXX) is not heed by the underlying Derby stream.
> [1]
> http://java.sun.com/j2se/1.5.0/docs/api/java/sql/ResultSet.html#getBinaryStream(int)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
