[
https://issues.apache.org/jira/browse/DERBY-6420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Haase updated DERBY-6420:
-----------------------------
Attachment: DERBY-6420-2.zip
DERBY-6420-2.diff
Thanks, Knut! I'm attaching DERBY-6420-2.diff and DERBY-6420-2.zip, with just
the change to DROP TABLE that you suggested. Hope this works. I did not try to
reorganize the two topics, to avoid possibly introducing more errors.
> Clarify how DROP statements work on trigger dependencies
> --------------------------------------------------------
>
> Key: DERBY-6420
> URL: https://issues.apache.org/jira/browse/DERBY-6420
> Project: Derby
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 10.11.0.0
> Reporter: Knut Anders Hatlen
> Assignee: Kim Haase
> Priority: Minor
> Attachments: DERBY-6420-2.diff, DERBY-6420-2.zip, DERBY-6420.diff,
> DERBY-6420.stat, DERBY-6420.zip
>
>
> Some of the DROP statement topics don't mention what happens if an object
> depended on by a trigger gets dropped. We should add this information. The
> behaviour should be more consistent after DERBY-2041.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
