db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deepa Remesh (JIRA)" <derby-...@db.apache.org>
Subject [jira] Created: (DERBY-1602) Handle cases where a statement in a procedure called by a trigger can cause trigger recursion
Date Thu, 27 Jul 2006 21:47:16 GMT
Handle cases where a statement in a procedure called by a trigger can cause trigger recursion
---------------------------------------------------------------------------------------------

                 Key: DERBY-1602
                 URL: http://issues.apache.org/jira/browse/DERBY-1602
             Project: Derby
          Issue Type: Improvement
          Components: SQL
            Reporter: Deepa Remesh


Following cases need to be handled:
* INSERT trigger which calls a procedure that performs an INSERT into the trigger table.
* UPDATE trigger which calls a procedure that performs an UPDATE into the trigger table
* DELETE trigger which calls a procedure that performs a DELETE from the trigger table.

Currently, the trigger firing will fail in all these cases as these are considered cases of
trigger recursion. But the SQL exception thrown is not very meaningful. Moreover, we will
need to clarify if this is the correct behaviour as there is some confusion as to what can
be classified as a recursive trigger. Some discussion about this has happened in DERBY-1261.
Once the behaviour is decided, these cases can be added to lang/procedureInTrigger.sql test.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message