Return-Path: X-Original-To: apmail-db-derby-dev-archive@www.apache.org Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 06F3410B06 for ; Wed, 4 Dec 2013 18:12:36 +0000 (UTC) Received: (qmail 83784 invoked by uid 500); 4 Dec 2013 18:12:35 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 83765 invoked by uid 500); 4 Dec 2013 18:12:35 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 83757 invoked by uid 99); 4 Dec 2013 18:12:35 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Dec 2013 18:12:35 +0000 Date: Wed, 4 Dec 2013 18:12:35 +0000 (UTC) From: "Kim Haase (JIRA)" To: derby-dev@db.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Reopened] (DERBY-6420) Clarify how DROP statements work on trigger dependencies MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DERBY-6420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim Haase reopened DERBY-6420: ------------------------------ Glad you noticed that, Knut. I'll file an additional patch. > 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.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)