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 "Kathey Marsden (JIRA)" <ji...@apache.org> on 2007/04/10 18:45:32 UTC

[jira] Created: (DERBY-2536) Convert lang/procedureInTrigger.sql to JUnit

Convert lang/procedureInTrigger.sql to JUnit
--------------------------------------------

                 Key: DERBY-2536
                 URL: https://issues.apache.org/jira/browse/DERBY-2536
             Project: Derby
          Issue Type: Task
          Components: Test
    Affects Versions: 10.3.0.0
            Reporter: Kathey Marsden
            Priority: Minor


Convert lang/procedureInTrigger.sql to JUnit

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


[jira] Commented: (DERBY-2536) Convert lang/procedureInTrigger.sql to JUnit

Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DERBY-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488169 ] 

Kathey Marsden commented on DERBY-2536:
---------------------------------------

I found a solution to the problem of verifying procedure calls.  It  seems to work to increment a static variable in the stored procedure, then check and reset it after it is called by the trigger.

> Convert lang/procedureInTrigger.sql to JUnit
> --------------------------------------------
>
>                 Key: DERBY-2536
>                 URL: https://issues.apache.org/jira/browse/DERBY-2536
>             Project: Derby
>          Issue Type: Task
>          Components: Test
>    Affects Versions: 10.3.0.0
>            Reporter: Kathey Marsden
>         Assigned To: Kathey Marsden
>            Priority: Minor
>
> Convert lang/procedureInTrigger.sql to JUnit

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


[jira] Assigned: (DERBY-2536) Convert lang/procedureInTrigger.sql to JUnit

Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kathey Marsden reassigned DERBY-2536:
-------------------------------------

    Assignee: Kathey Marsden

> Convert lang/procedureInTrigger.sql to JUnit
> --------------------------------------------
>
>                 Key: DERBY-2536
>                 URL: https://issues.apache.org/jira/browse/DERBY-2536
>             Project: Derby
>          Issue Type: Task
>          Components: Test
>    Affects Versions: 10.3.0.0
>            Reporter: Kathey Marsden
>         Assigned To: Kathey Marsden
>            Priority: Minor
>
> Convert lang/procedureInTrigger.sql to JUnit

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


[jira] Commented: (DERBY-2536) Convert lang/procedureInTrigger.sql to JUnit

Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DERBY-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487922 ] 

Kathey Marsden commented on DERBY-2536:
---------------------------------------

I have the same issue of not being able to verify calls for "CONTAINS SQL" and "READ SQL DATA".  CONTAINS SQL is particularly curious.  It says  "Indicates that SQL statements that neither read nor modify SQL data can be executed by the stored procedure"  I wonder what kind of  SQL Statement would neither read nor write data.  The existing test has only getConnection() for CONTAINS SQL.
 

> Convert lang/procedureInTrigger.sql to JUnit
> --------------------------------------------
>
>                 Key: DERBY-2536
>                 URL: https://issues.apache.org/jira/browse/DERBY-2536
>             Project: Derby
>          Issue Type: Task
>          Components: Test
>    Affects Versions: 10.3.0.0
>            Reporter: Kathey Marsden
>         Assigned To: Kathey Marsden
>            Priority: Minor
>
> Convert lang/procedureInTrigger.sql to JUnit

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


[jira] Closed: (DERBY-2536) Convert lang/procedureInTrigger.sql to JUnit

Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kathey Marsden closed DERBY-2536.
---------------------------------


> Convert lang/procedureInTrigger.sql to JUnit
> --------------------------------------------
>
>                 Key: DERBY-2536
>                 URL: https://issues.apache.org/jira/browse/DERBY-2536
>             Project: Derby
>          Issue Type: Task
>          Components: Test
>    Affects Versions: 10.3.0.0
>            Reporter: Kathey Marsden
>         Assigned To: Kathey Marsden
>            Priority: Minor
>             Fix For: 10.3.0.0
>
>
> Convert lang/procedureInTrigger.sql to JUnit

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


[jira] Resolved: (DERBY-2536) Convert lang/procedureInTrigger.sql to JUnit

Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kathey Marsden resolved DERBY-2536.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 10.3.0.0

> Convert lang/procedureInTrigger.sql to JUnit
> --------------------------------------------
>
>                 Key: DERBY-2536
>                 URL: https://issues.apache.org/jira/browse/DERBY-2536
>             Project: Derby
>          Issue Type: Task
>          Components: Test
>    Affects Versions: 10.3.0.0
>            Reporter: Kathey Marsden
>         Assigned To: Kathey Marsden
>            Priority: Minor
>             Fix For: 10.3.0.0
>
>
> Convert lang/procedureInTrigger.sql to JUnit

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


[jira] Commented: (DERBY-2536) Convert lang/procedureInTrigger.sql to JUnit

Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DERBY-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487899 ] 

Kathey Marsden commented on DERBY-2536:
---------------------------------------

This test has a case where it needs to count the number of executions of a NO SQL  procedure in a trigger.
This was tested with a System.out.println statement in the old SQL test, e.g.

  public static void zeroArg() {
                System.out.println("zeroArg() called");
        }
        
The sql is a follows:

create procedure proc_no_sql() parameter style java language java NO SQL external name 'org.apache.derbyTesting.functionTests.tests.lang.ProcedureInTriggerTest.zeroArg

create trigger after_stmt_trig_no_sql AFTER insert on t2 for each STATEMENT call proc_no_sql()

insert into t2 values (1,2), (2,4);

I want to check  that zeroArg was called only once but can't figure out how to do it without adding sql to insert into a table.  Any thoughts on this?


> Convert lang/procedureInTrigger.sql to JUnit
> --------------------------------------------
>
>                 Key: DERBY-2536
>                 URL: https://issues.apache.org/jira/browse/DERBY-2536
>             Project: Derby
>          Issue Type: Task
>          Components: Test
>    Affects Versions: 10.3.0.0
>            Reporter: Kathey Marsden
>         Assigned To: Kathey Marsden
>            Priority: Minor
>
> Convert lang/procedureInTrigger.sql to JUnit

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