[ https://issues.apache.org/jira/browse/DERBY-6454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13890790#comment-13890790 ]
Knut Anders Hatlen commented on DERBY-6454: ------------------------------------------- Thanks, Kim. This looks like an improvement to me. One more clarification may be needed: "The DROP TABLE statement will also generate an error (...) if a trigger references the table in its trigger action." It would be more precise to say "if a trigger _defined on another table_ references the table in its trigger action." > DROP TABLE documentation could clarify how triggers are handled > --------------------------------------------------------------- > > Key: DERBY-6454 > URL: https://issues.apache.org/jira/browse/DERBY-6454 > Project: Derby > Issue Type: Bug > Components: Documentation > Affects Versions: 10.10.1.1 > Reporter: Dyre Tjeldvoll > Assignee: Kim Haase > Priority: Minor > Attachments: DERBY-6454.diff, rrefsqlj34148.html > > > The description of the DROP TABLE command first asserts that > "Triggers, constraints (primary, unique, check and references from the table > being dropped) and indexes on the table are silently dropped. " > And then > "The DROP TABLE statement will also generate an error if the table is used in > a view or trigger." > This is perfectly correct, but I think it would have been easier to grasp if > the text had spelled out that triggers which are defined on the table being > dropped are dropped automatically, but that the existence of triggers which > reference the table being dropped in their trigger action will cause an error. -- This message was sent by Atlassian JIRA (v6.1.5#6160)