[ http://issues.apache.org/jira/browse/DERBY-551?page=comments#action_12320932 ]
Daniel John Debrunner commented on DERBY-551: --------------------------------------------- FYI - Cloudscape 3.5 supported a CALL statement but did not support procedures. Not sure what effect this will have on re-enabling the CALL statement in triggers, apart from the combination is unlikely to have been tested. > 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 > > 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
