You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Knut Anders Hatlen (JIRA)" <ji...@apache.org> on 2008/07/02 11:30:45 UTC
[jira] Commented: (DERBY-3749) in holdable cursor selecting
multiple rows with streaming blobs and clobs a commit may cause later row's
streams to be broken
[ https://issues.apache.org/jira/browse/DERBY-3749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609850#action_12609850 ]
Knut Anders Hatlen commented on DERBY-3749:
-------------------------------------------
I think this is a duplicate of DERBY-1511.
> 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.