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 Wed, 09 May 2007 18:15: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-2.diff

Attaching patch which adds a JUnit fixture which tests whether an UpdateResultSet is able
to detect changes in isolation level between executions. The test passes on trunk, but fails
when the patch for DERBY-827 is applied (it continues with table-level locking after changing
isolation level from serializable to read committed).

> 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
>          Components: Performance, SQL
>    Affects Versions: 10.3.0.0
>            Reporter: Knut Anders Hatlen
>         Assigned To: Knut Anders Hatlen
>         Attachments: derby-2597-1.diff, derby-2597-1.stat, derby-2597-2.diff
>
>
> 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.


Mime
View raw message