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 "Daniel John Debrunner (JIRA)" <ji...@apache.org> on 2008/02/08 21:34:08 UTC

[jira] Closed: (DERBY-3391) CompilerContext contains old logic to restore the entry isolation level of the connection after compilation

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

Daniel John Debrunner closed DERBY-3391.
----------------------------------------

       Resolution: Fixed
    Fix Version/s: 10.4.0.0

Revision: 619981 in trunk removes the dead code.

> CompilerContext contains old logic to restore the entry isolation level of the connection after compilation
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3391
>                 URL: https://issues.apache.org/jira/browse/DERBY-3391
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>            Reporter: Daniel John Debrunner
>            Assignee: Daniel John Debrunner
>            Priority: Minor
>             Fix For: 10.4.0.0
>
>
> CompilerContext saves the isolation level of the LanguageConnectionContext (LCC) when it is pushed and restores it when it is popped. However there is no mechanism for the isolation level to change during compilation. Isolation level can only be changed by a Connection.setTransactionIsolation() or the SET ISOLATION SQL statement.

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