[ http://issues.apache.org/jira/browse/DERBY-551?page=comments#action_12420629 ]
Daniel John Debrunner commented on DERBY-551: --------------------------------------------- Just to clarify, it seems that this patch does not disable MODIFIES SQL DATA procedures in a before trigger, only DDL statements in all triggers and DML actions in a before trigger. Is that correct? You indicate that the checks might move, once the code has settled i think the comments in InternalTriggerExecutionContext.validateStatement could be enhanced with your knowledge. For example adding commeents to the DDL check that DDL statements as the trigger's action statement are disallowed by the parser and the check is for statements executed by procedures executed within a trigger context. Similar comments for before triggers, making it clear the multiple ways DML is disallowed, e.g. currently the DML is disallowed at compile time. > Allow invoking java stored procedures from inside a trigger. Make CALL a > valid statement in the trigger body. > ------------------------------------------------------------------------------------------------------------- > > Key: DERBY-551 > URL: http://issues.apache.org/jira/browse/DERBY-551 > Project: Derby > Type: New Feature > Components: SQL > Versions: 10.1.1.0 > Environment: All platforms > Reporter: Satheesh Bandaram > Assignee: Deepa Remesh > Fix For: 10.2.0.0 > Attachments: ProcedureInTrigger_Tests_v1.html, derby-551-draft1.diff, > derby-551-draft1.status, derby-551-draft2.status, derby-551-draft3.diff, > derby-551-draft3.status, derby-551-patch1-v1.diff, > derby-551-patch1-v1.status, derby-551draft2.diff > > Derby currently doesn't allow CALL statement to be used in a trigger body. It > would be great to allow java stored procedure invocation inside a trigger. > Since Derby doesn't have SQL procedure language, triggers can only execute a > single SQL statement. If we allow stored procedures in triggers, it would be > possible to write a trigger that involves more than just one SQL statement. > Functions are currently allowed, but they are read-only. > I believe it is fairly easy to support this enhancement. Need good amount of > testing though. -- 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
