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 8E29F1052F for ; Mon, 10 Feb 2014 15:59:20 +0000 (UTC) Received: (qmail 22498 invoked by uid 500); 10 Feb 2014 15:59:20 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 22472 invoked by uid 500); 10 Feb 2014 15:59:20 -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 22458 invoked by uid 99); 10 Feb 2014 15:59:19 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Feb 2014 15:59:19 +0000 Date: Mon, 10 Feb 2014 15:59:19 +0000 (UTC) From: "Kim Haase (JIRA)" To: derby-dev@db.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (DERBY-6454) DROP TABLE documentation could clarify how triggers are handled 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-6454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim Haase resolved DERBY-6454. ------------------------------ Resolution: Fixed Fix Version/s: 10.11.0.0 Issue & fix info: (was: Patch Available) Thanks, Knut! Committed patch DERBY-6454-2.diff to documentation trunk at revision 1566663. I'm not merging this to the 10.10 branch because of conflicts. > DROP TABLE documentation could clarify how triggers are handled > --------------------------------------------------------------- > > Key: DERBY-6454 > URL: https://issues.apache.org/jira/browse/DERBY-6454 > Project: Derby > Issue Type: Bug > Components: Documentation > Affects Versions: 10.10.1.1 > Reporter: Dyre Tjeldvoll > Assignee: Kim Haase > Priority: Minor > Fix For: 10.11.0.0 > > Attachments: DERBY-6454-2.diff, DERBY-6454.diff, rrefsqlj34148.html, rrefsqlj34148.html > > > 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. -- This message was sent by Atlassian JIRA (v6.1.5#6160)