Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <50A2E0B6.2080503@sbcglobal.net>
Date: Tue, 13 Nov 2012 16:07:18 -0800
From: Katherine Marsden <kmarsdenderby@sbcglobal.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Derby Discussion <derby-user@db.apache.org>
Subject: Re: How to reset Derby Database in JVM
References: <1349919328.3013.YahooMailNeo@web162802.mail.bf1.yahoo.com>
 <5076B913.2090803@oracle.com> <34676336.post@talk.nabble.com>
In-Reply-To: <34676336.post@talk.nabble.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 11/13/2012 3:27 PM, Oskar Zinger wrote:
> Hi Rick,
>
> Thank you for the pointers to the right places in the documentation.
>
> Here is what I used:
> Shutting down the system:
> http://db.apache.org/derby/docs/10.8/devguide/tdevdvlp20349.html
> Shutting down Derby or an individual database:
> http://db.apache.org/derby/docs/10.8/devguide/tdevdvlp40464.html
>
> I am using Derby Network Server... and I think it would have helped if the
> documentation mentioned somewhere that this same approach would work for
> Client / Server deployment of Derby. Somehow it seemed to me this would have
> only worked for an Embedded deployment of Derby.
I think that it will only work really well for Embedded. Shutting down 
remotely can lead to protocol errors and also prevent you from getting 
the nested exception for the SQLException returned because the system is 
shutdown.

  If you are using embedded Server I would recommend using the embedded 
URL if you can.