[ http://issues.apache.org/jira/browse/DERBY-1505?page=all ]
Rick Hillegas updated DERBY-1505:
---------------------------------
Urgency: Low
> Reference Manual - Limitations of triggered-SQL-statement do not match
> current behaviour
> ----------------------------------------------------------------------------------------
>
> Key: DERBY-1505
> URL: http://issues.apache.org/jira/browse/DERBY-1505
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.2.0.0
> Reporter: Deepa Remesh
> Priority: Minor
> Fix For: 10.2.0.0
>
>
> Reference manual (Section CREATE TRIGGER statement -->
> Triggered-SQL-statement ) needs to be updated to match the current behaviour:
> 1) I think the following statements are not fully correct:
> # It must not create, alter, or drop the table upon which the trigger is
> defined.
> # It must not add an index to or remove an index from the table on which
> the trigger is defined.
> # It must not add a trigger to or drop a trigger from the table upon which
> the trigger is defined.
> These actions are not allowed on "any" table not just the " table upon which
> the trigger is defined". In general, the code does not allow execution of any
> DDL statement within a trigger. I think we can replace the above statements
> with something like "It cannot contain DDL statements."
> 2) The following statement is not valid:
> "The triggered-SQL-statement can reference database objects other than the
> table upon which the trigger is declared."
> The triggered-SQL-statement can reference the table upon which the trigger is
> declared. Hence this statement can be removed.
> It would be good if someone familiar in this area can confirm the proposed
> changes are okay.
--
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
