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 "Mike Matrigali (JIRA)" <ji...@apache.org> on 2008/07/01 23:20:45 UTC
[jira] Created: (DERBY-3749) in holdable cursor selecting multiple
rows with streaming blobs and clobs a commit may cause later row's streams
to be broken
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
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.
[jira] Updated: (DERBY-3749) in holdable cursor selecting multiple
rows with streaming blobs and clobs a commit may cause later row's streams
to be broken
Posted by "Mike Matrigali (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Matrigali updated DERBY-3749:
----------------------------------
I anyone gets a chance to look at this the first thing I would track down is if this is a bulk fetch issue. By that I mean are
N streams getting created for N rows before even the first is returned to the user. For performance bulk fetch is the usual
way language gets rows out of the store. Then when the commit happens each
of these "open" streams gets closed.
Reading through the code I don't think these streams have any support for holdability. Most of the hodability support is
located in the language and access layer. For instance in the case of an access fetch loop there is code everytime the
loop is reentered to check if it is a holdable cursor and if so to reopen the underlying resource.
My assumption is that this has been broken for many releases, but have not had a chance to check yet.
> 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.
[jira] Resolved: (DERBY-3749) in holdable cursor selecting multiple
rows with streaming blobs and clobs a commit may cause later row's streams
to be broken
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Knut Anders Hatlen resolved DERBY-3749.
---------------------------------------
Resolution: Duplicate
There hasn't been any objections to my comment about this issue being a duplicate of DERBY-1511, so I'm setting resolution to "Duplicate".
> 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.
[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
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (DERBY-3749) in holdable cursor selecting multiple
rows with streaming blobs and clobs a commit may cause later row's streams
to be broken
Posted by "Mike Matrigali (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Issue Comment Edited: (DERBY-3749) in holdable cursor
selecting multiple rows with streaming blobs and clobs a commit may cause
later row's streams to be broken
Posted by "Mike Matrigali (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609713#action_12609713 ]
mikem edited comment on DERBY-3749 at 7/1/08 2:35 PM:
---------------------------------------------------------------
I ran into this bug while trying to fix DERBY-3650 (thus the name of the attached test case). The testBlobSelect*Commit() and testClobSelect*Commit() cases where a commit is performed after finishing with the object show this bug. If I get time I will narrow down/rename the test, but
figured it was better to post what I had than wait.
I am pretty sure that this commit issue is separate from the multiple reference issue, that is the point of DERBY-3650.
was (Author: mikem):
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.