Return-Path: 
 <derby-dev-return-50217-apmail-db-derby-dev-archive=db.apache.org@db.apache.org>
Delivered-To: apmail-db-derby-dev-archive@www.apache.org
Received: (qmail 40721 invoked from network); 24 Oct 2007 06:05:05 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 24 Oct 2007 06:05:05 -0000
Received: (qmail 74807 invoked by uid 500); 24 Oct 2007 06:04:52 -0000
Delivered-To: apmail-db-derby-dev-archive@db.apache.org
Received: (qmail 74772 invoked by uid 500); 24 Oct 2007 06:04:51 -0000
Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:derby-dev-help@db.apache.org>
List-Unsubscribe: <mailto:derby-dev-unsubscribe@db.apache.org>
List-Post: <mailto:derby-dev@db.apache.org>
List-Id: <derby-dev.db.apache.org>
Reply-To: <derby-dev@db.apache.org>
Delivered-To: mailing list derby-dev@db.apache.org
Received: (qmail 74763 invoked by uid 99); 24 Oct 2007 06:04:51 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Oct 2007 23:04:51 -0700
X-ASF-Spam-Status: No, hits=2.0 required=10.0
	tests=HTML_MESSAGE,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of dimp20@gmail.com designates
 64.233.184.231 as permitted sender)
Received: from [64.233.184.231] (HELO wr-out-0506.google.com) (64.233.184.231)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Oct 2007 06:04:55 +0000
Received: by wr-out-0506.google.com with SMTP id 70so83908wra
        for <derby-dev@db.apache.org>; Tue, 23 Oct 2007 23:04:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=beta;
        h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type;
        bh=ANLDyjaKD/utHZxa+mCXNSoB8oC1RrZyKXPvjM2RCg0=;
        b=qu7uLU7kaXEshrWVezlj4tAL44jEplYS9DAiFtjtFsMWgeLIdguSflGUXaHgF2iWVxe771eZppjCM7yB0EALNYthwOsen7LquSOeVz/kDI+vNw7pGLIDK8yAgJHx8I5EPMPaS4+BE+F1Sgxlo+GUbiYepDm4zeZFfwMsgqHzyxA=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:mime-version:content-type;
        b=XUCa9MZ6EfNpoPwZ1KYAdv3606aAQ+dq2Oh9qzFtDYj50wAoBbCYcP7H2JIgy0cKmZcXBZ+0pq3k21MTbmam6MOyavyCOtd+uJQe327pF8nofrvuVRpl33ITffj2QL9aAnTaBOrTgbb893nzXCGbCkZWfrQu99C1hBzfDqsf6A4=
Received: by 10.142.139.19 with SMTP id m19mr22216wfd.1193205873289;
        Tue, 23 Oct 2007 23:04:33 -0700 (PDT)
Received: by 10.142.245.13 with HTTP; Tue, 23 Oct 2007 23:04:33 -0700 (PDT)
Message-ID: <a1856f970710232304o7ccb802dj69fadf8e45f78355@mail.gmail.com>
Date: Tue, 23 Oct 2007 23:04:33 -0700
From: "Dimple Bhatia" <dimp20@gmail.com>
To: derby-dev@db.apache.org
Subject: Dropping a table referenced in a view
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_3171_1789431.1193205873263"
X-Virus-Checked: Checked by ClamAV on apache.org

------=_Part_3171_1789431.1193205873263
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi,
I see that in derby if a table is being referenced in a view, we need to
drop the view first and then only we can drop the table being referenced in
a view. But in DB2, we do allow users to drop the table and we mark the view
invalid. So just wondering why we don't the same in Derby and are there any
plans of doing so soon?

Thanks
Dimple

------=_Part_3171_1789431.1193205873263
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div>Hi,</div>
<div>I see that in derby if a table is being referenced in a view, we need to drop the view first and then only we can drop the table being referenced in a view. But in DB2, we do allow users to drop the table and we mark the view invalid. So just wondering why we don&#39;t the same in Derby and are there any plans of doing so soon?
</div>
<div>&nbsp;</div>
<div>Thanks</div>
<div>Dimple</div>
<div>&nbsp;</div>

------=_Part_3171_1789431.1193205873263--