[
https://issues.apache.org/jira/browse/DERBY-3749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-3749:
----------------------------------
Attachment: Derby3650Test.java
I ran into this bug while trying to fix DERBY-3650. The testBlobSelect() and
testClobSelect() cases where a commit is performed after finishing with the
object show this bug. If I get time I will narrow down the test, but
figured it was better to post what I had than wait.
I pretty sure that this commit issue is separate from the multiple reference
issue.
> in holdable cursor selecting multiple rows with streaming blobs and clobs a
> commit may cause later row's streams to be broken
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3749
> URL: https://issues.apache.org/jira/browse/DERBY-3749
> Project: Derby
> Issue Type: Bug
> Affects Versions: 10.5.0.0
> Reporter: Mike Matrigali
> Priority: Minor
> Attachments: Derby3650Test.java
>
>
> In a query returning multiple rows from a table, where later rows in the
> select loop after the commit contain streaming clobs or blobs a commit may
> attempts to get at those streams after the commit to fail with a:
> 3)java.sql.SQLException: The data in this BLOB or CLOB is no longer
> available.
> The BLOB/CLOB's transaction may be committed, or its connection is closed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
