[ http://issues.apache.org/jira/browse/DERBY-1551?page=comments#action_12427629 ] David Van Couvering commented on DERBY-1551: --------------------------------------------
There are many cases where the same SQL State can have different messages. I agree they should be separate rows. There is no "unique identifier", that is different for each message, that is exposed to the user. > 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
