[
https://issues.apache.org/jira/browse/DERBY-6420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13918349#comment-13918349
]
Myrna van Lunteren commented on DERBY-6420:
-------------------------------------------
setting backport reject to 10.10 to match the flag for DERBY-2041, part of this
might be ok to backport, but it will be tricky to figure out which parts.
> 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
> Labels: derby_backport_reject_10_10
> Fix For: 10.11.0.0
>
> Attachments: DERBY-6420-2.diff, DERBY-6420-2.zip, DERBY-6420-3.diff,
> DERBY-6420.diff, DERBY-6420.stat, DERBY-6420.zip, rrefsqljdropsynonym.html
>
>
> 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.2#6252)
