[DERBY-6454] DROP TABLE documentation could clarify how triggers are handled

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.10.1.1
• Fix Version/s: 10.11.1.1
• Component/s: Documentation
• Labels: derby_backport_reject_10_10
• Assignee: Camilla Haase
• Reporter: Dyre Tjeldvoll
• Created: 09/Jan/14 15:30
• Updated: 03/Sep/14 06:46
• Resolved: 10/Feb/14 15:57

Description

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.