db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2597) Language result sets should not reuse current isolation level across executions
Date Mon, 30 Apr 2007 12:16:15 GMT

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

Knut Anders Hatlen updated DERBY-2597:

    Attachment: derby-2597-1.stat

The attached patch (derby-2597-1) solves the problem for HashScanResultSet, TableScanResultSet
and LastIndexKeyResultSet (and their sub-classes) by refreshing the isolation level on each
open. Since the code that found the correct isolation level and lock mode was almost identical
in all those classes, I created a common base class for them (ScanResultSet) and removed the
duplicated code.

With this patch, ResultSetsFromPreparedStatementTest runs cleanly even with the DERBY-827
patch applied.

Derbyall and suites.All ran cleanly on Solaris 10, Java 1.6.

> Language result sets should not reuse current isolation level across executions
> -------------------------------------------------------------------------------
>                 Key: DERBY-2597
>                 URL: https://issues.apache.org/jira/browse/DERBY-2597
>             Project: Derby
>          Issue Type: Sub-task
>    Affects Versions:
>            Reporter: Knut Anders Hatlen
>         Assigned To: Knut Anders Hatlen
>         Attachments: derby-2597-1.diff, derby-2597-1.stat
> Some of the language result sets cache the current isolation level in their constructors.
To allow reuse of the result sets, they should check the isolation level each time they are
opened. Currently, this affects HashScanResultSet, TableScanResultSet, LastIndexKeyResultSet
and UpdateResultSet (and their sub-classes).

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message