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 "Dag H. Wanvik (JIRA)" <ji...@apache.org> on 2013/06/27 16:12:20 UTC

[jira] [Updated] (DERBY-6276) Convert lang/DB2IsolationLevels.sql to JUnit

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

Dag H. Wanvik updated DERBY-6276:
---------------------------------

    Attachment: DB2IsolationLevelsTest.stat
                DB2IsolationLevelsTest.diff

Attaching a patch with a converted test.
I noticed some weird functionality here:

By default "values current isolation" returns "CS", i.e. read committed. However, we support a statement "set isolation reset", after which the values above call returns a single blank.

Does anyone know the story "reset"? Semantics and why we need it? Is it a DB2-ism?




                
> Convert lang/DB2IsolationLevels.sql to JUnit
> --------------------------------------------
>
>                 Key: DERBY-6276
>                 URL: https://issues.apache.org/jira/browse/DERBY-6276
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>            Reporter: Dag H. Wanvik
>         Attachments: DB2IsolationLevelsTest.diff, DB2IsolationLevelsTest.stat
>
>


--
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