[ http://issues.apache.org/jira/browse/DERBY-551?page=all ]

Deepa Remesh updated DERBY-551:
-------------------------------

    Attachment: derby-551-patch2-v1.diff

Thanks Dan for committing patch1. 

Based on Dan's suggestion, I am working on adding a check to the parser for 
disallowing procedures that modify SQL data in before triggers. However, this 
patch is not quite ready.

Meantime, I am attaching a follow-up patch 'derby-551-patch2-v1.diff' which 
adds more comments to InternalTriggerExecutionContext.validateStatement. This 
patch only adds comments and does not change any code. Please take a look at it 
and commit if okay.

> 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-551-patch2-v1.diff, 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

Reply via email to