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 2007/05/11 10:40:15 UTC
[jira] Resolved: (DERBY-2597) Language result sets should not reuse
current isolation level across executions
[ https://issues.apache.org/jira/browse/DERBY-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Knut Anders Hatlen resolved DERBY-2597.
---------------------------------------
Resolution: Fixed
Fix Version/s: 10.3.0.0
Derby Info: (was: [Patch Available])
Committed derby-2597-3 with revision 537128.
> 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
> Fix For: 10.3.0.0
>
> Attachments: derby-2597-1.diff, derby-2597-1.stat, derby-2597-2.diff, derby-2597-3.diff, derby-2597-3.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.