[ http://issues.apache.org/jira/browse/DERBY-1551?page=comments#action_12427568 ] Laura Stewart commented on DERBY-1551: --------------------------------------
Deepa - for 42Z9D, each message has only one row in a table. Is the text you want me to add actually part of the message text? If it is not part of the message text, then it doesn't belong in the table. If this is an explanation, like a note, then it should go somewhere else. If the text is part of the message and you just want me to force a carriage return, I can do that. > 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
