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] Commented: (DERBY-1551) Update documentation to indicate procedures can be called from triggers (DERBY-551)
Date Fri, 11 Aug 2006 20:44:14 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1551?page=comments#action_12427623 ] 
            
Deepa Remesh commented on DERBY-1551:
-------------------------------------

The text I added is a different message for the same SQLState "42Z9D".  So there can be two
different messages in two different scenarios - both with same SQL state. 

I still think it may be better to add it as another row for same SQLState. There can be multiple
rows in the table for same SQLState (e.g. 42815). 
It would be great if someone else can comment if this is the right way to handle this. 

> Update documentation to indicate procedures can be called from triggers (DERBY-551)
> -----------------------------------------------------------------------------------
>
>                 Key: DERBY-1551
>                 URL: http://issues.apache.org/jira/browse/DERBY-1551
>             Project: Derby
>          Issue Type: Task
>          Components: Documentation
>            Reporter: Deepa Remesh
>         Assigned To: Laura Stewart
>             Fix For: 10.2.0.0
>
>         Attachments: derby1551_ref.diff, derby1551_ref_html.zip
>
>
> Derby Reference manual has to be updated with following information:
> * Section "CREATE TRIGGER statement" --> "Triggered-SQL-statement"
>    - The following line "It must not execute a CALL statement." needs to be removed
>    - The following line "Before triggers cannot have INSERT, UPDATE or DELETE statements
as their action." needs to be replaced to indicate before triggers also cannot call procedures
that modify SQL data. It can be replaced with something like ""Before triggers cannot have
INSERT, UPDATE or DELETE statements or calls to procedures that modify SQL data as their action."
> * Section "SQLState and error message reference"
>    - Message text for X0Y69 has to be changed to "<value> is not supported in trigger
<triggerName>."
>    - An additional row to be added for 42Z9D with following message text "Procedures
that modify SQL data are not allowed in BEFORE triggers."
> If there are any other places where the documentation needs to be updated for DERBY-551,
please post it to this issue.

-- 
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