db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-4800) Allow bulk scan of LOB tables with holdable cursors
Date Fri, 28 Sep 2012 18:29:07 GMT

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

Mamta A. Satoor updated DERBY-4800:
-----------------------------------

    Urgency: Normal
     Labels: derby_triage10_10  (was: )
    
> Allow bulk scan of LOB tables with holdable cursors
> ---------------------------------------------------
>
>                 Key: DERBY-4800
>                 URL: https://issues.apache.org/jira/browse/DERBY-4800
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 10.7.1.1
>            Reporter: Knut Anders Hatlen
>            Priority: Minor
>              Labels: derby_triage10_10
>
> DERBY-1511 disabled bulk scans for tables with LOBs if the cursor was holdable. This
was done to work around a bug, but it had a very negative impact on queries that scanned tables
that contained relatively small LOBs. It would be good if we could find a safe way to re-enable
bulk scans for these queries.
> The problem now is that the lob containers are closed on the transaction boundaries,
so the buffered values will be dead on arrival when we call next() after a commit(). If we
could find a way to make the containers survive across the transaction boundary, or make it
possible to reopen the container, it should be safe to re-enable the bulk scans.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message