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-4521) Stream passed out to user does not heed close, allowing reads after next ResultSet#getXXX
Date Fri, 22 Jan 2010 17:49:21 GMT

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

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

    Attachment: repro.diff

Uploading a repro, as a patch to ResultSetStreamTest which shows both that the embedded driver
behaves incorrectly and that the client driver behaves correctly.


> 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
>            Reporter: Dag H. Wanvik
>            Priority: Minor
>         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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message