Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 64649 invoked from network); 17 Nov 2009 17:35:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 17 Nov 2009 17:35:44 -0000 Received: (qmail 63051 invoked by uid 500); 17 Nov 2009 17:35:44 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 63013 invoked by uid 500); 17 Nov 2009 17:35:44 -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 63005 invoked by uid 99); 17 Nov 2009 17:35:44 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Nov 2009 17:35:44 +0000 X-ASF-Spam-Status: No, hits=-4.0 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [192.18.6.24] (HELO gmp-eb-inf-2.sun.com) (192.18.6.24) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Nov 2009 17:35:34 +0000 Received: from fe-emea-09.sun.com (gmp-eb-lb-1-fe1.eu.sun.com [192.18.6.7] (may be forged)) by gmp-eb-inf-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id nAHHZD8N026987 for ; Tue, 17 Nov 2009 17:35:13 GMT MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from conversion-daemon.fe-emea-09.sun.com by fe-emea-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KT900J00KRRWU00@fe-emea-09.sun.com> for derby-dev@db.apache.org; Tue, 17 Nov 2009 17:35:06 +0000 (GMT) Received: from localhost ([unknown] [129.159.112.134]) by fe-emea-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KT9009YAKUHHN30@fe-emea-09.sun.com> for derby-dev@db.apache.org; Tue, 17 Nov 2009 17:35:06 +0000 (GMT) Date: Tue, 17 Nov 2009 18:35:05 +0100 From: Knut Anders Hatlen Subject: Re: Confusing error message on boot? In-reply-to: <4B02C1C8.3020805@Sun.COM> Sender: Knut.Hatlen@Sun.COM To: derby-dev@db.apache.org Message-id: Organization: Sun Microsystems References: <4B02C1C8.3020805@Sun.COM> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (usg-unix-v) X-Virus-Checked: Checked by ClamAV on apache.org Kristian Waagan writes: > Hi, > > Working on the drop database feature (DERBY-4428), I noticed this: > > ij> connect 'jdbc:derby:memory:test;shutdown=true;drop=true'; > ERROR XJ048: Conflicting boot attributes specified: shutdown, drop > ij> connect 'jdbc:derby:memory:test;shutdown=true;create=true'; > ERROR XJ004: Database 'memory:test' not found. > > > The error XJ0048 is new (I'm considering adding it). > However, note that if you specify both shutdown and create you're told > that the database doesn't exist. What happens is that the shutdown > attribute takes precedence over the create attribute. > > Should we change this to show something like XJ048? That sounds like a more reasonable response, at least. > Can we change it without causing trouble for existing applications? The potential incompatibility here, if I understand correctly, is that if the database 'test' is booted when that command is issued, the command currently shuts down the database, whereas with the suggested change it reports that the attributes are in conflict and leaves the database booted? The combination of shutdown=true and create=true doesn't make much sense (unless it meant create a database and shut it down cleanly, which it doesn't). So if we haven't documented anywhere that shutdown takes precedence over create, I wouldn't think it's very problematic to disallow the combination. -- Knut Anders