db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tiago R. Espinha (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3839) Convert "org.apache.derbyTesting.functionTests.tests.store.holdCursorJDBC30.sql" to junit.
Date Wed, 29 Apr 2009 16:09:30 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12704174#action_12704174

Tiago R. Espinha commented on DERBY-3839:

This issue is currently blocked by DERBY-4198.

I was reading through the DERBY-3801 and Myrna says:
"I think you believe a ScriptTest is a 'tool' to convert the test to junit, and it may have
started as a quick way to run certain .sql ways in junit, but it is currently the best way
to execute the language constructs that are specific to ij.
Yes, we have in the charter to use only standard SQL, but there are some extensions that are
specific to Derby and they have to be tested also.

Language clauses as "get cursor with hold", "next", "update where current of".
So, it's important to keep a test that verifies appropriate behavior when such things are
used in ij. Thus, we *do* need a HoldCursorIJTest, but it should be extending ScriptTestCase."

Considering that this test does rely a lot on the GET CURSOR WITH HOLD and it has its share
of UPDATE WHERE CURRENT OF, should this test be extending ScriptTest as well rather than a

> Convert "org.apache.derbyTesting.functionTests.tests.store.holdCursorJDBC30.sql" to junit.

> -------------------------------------------------------------------------------------------
>                 Key: DERBY-3839
>                 URL: https://issues.apache.org/jira/browse/DERBY-3839
>             Project: Derby
>          Issue Type: Test
>          Components: Test
>            Reporter: Junjie Peng
>            Assignee: Tiago R. Espinha
>         Attachments: derby-3839-1.patch, derby-3839-1.stat, derby-3839.patch, ReproHoldCursorBug.java,

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

View raw message