You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Knut Anders Hatlen (JIRA)" <ji...@apache.org> on 2013/12/05 08:38:36 UTC

[jira] [Closed] (DERBY-6420) Clarify how DROP statements work on trigger dependencies

     [ https://issues.apache.org/jira/browse/DERBY-6420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Knut Anders Hatlen closed DERBY-6420.
-------------------------------------


Verified that the fixes have made it to the latest alpha manuals. Closing the issue.

> 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
>             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.1#6144)