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 "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2013/08/14 00:08:47 UTC
[jira] [Commented] (DERBY-6276) Convert lang/DB2IsolationLevels.sql
to JUnit
[ https://issues.apache.org/jira/browse/DERBY-6276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13738906#comment-13738906 ]
Myrna van Lunteren commented on DERBY-6276:
-------------------------------------------
This reset might indeed be a DB2-ism, judging by the name of the test...Assuming it's not in the SQL Standard (I don't have access to that right now...). It matches the timing, this test code was added after IBM acquired Informix (which had acquired Cloudscape), but before the contribution to Apache.
Judging from the manuals I saw, it is doing the same in DB2; blanking out the contents of a variable that holds the value of 'current isolation'.
Assuming it's not in the SQL Standard, how do we normally handle additions to it? Taking it out now could (although unlikely, imho, but still) cause incompatibility trouble...
> 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