[
https://issues.apache.org/jira/browse/DERBY-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamta A. Satoor updated DERBY-1602:
-----------------------------------
Urgency: Low
Labels: derby_triage10_11 (was: )
> Handle cases where a statement in a procedure called by a trigger can cause
> trigger recursion
> ---------------------------------------------------------------------------------------------
>
> Key: DERBY-1602
> URL: https://issues.apache.org/jira/browse/DERBY-1602
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Reporter: Deepa Remesh
> Labels: derby_triage10_11
>
> 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, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
