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: pass (asf.osuosl.org: local policy)
Subject: Re: [SHUTDOWN] Should I shutdown embedded data base ?
From: yves pielusenet <yvespielusenet@free.fr>
To: Derby Discussion <derby-user@db.apache.org>
In-Reply-To: <442B942E.9020404@sun.com>
References: <1143645437.7150.35.camel@localhost.localdomain>
	 <442AC54B.2000302@gmail.com>
	 <1143705471.6786.5.camel@localhost.localdomain>  <442B942E.9020404@sun.com>
Content-Type: text/plain; charset=ISO-8859-1
Date: Thu, 30 Mar 2006 10:29:33 +0200
Message-Id: <1143707373.6786.17.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit

Le jeudi 30 mars 2006 � 10:17 +0200, Oystein Grovlen - Sun Norway a
�crit :
> yves pielusenet wrote:
> 
> > Thank you for your answer :)
> > So, since I use an embedded database, should I use the shutdown command
> > (database shutdown nor derby shutdown) everytime I do
> > Connection.close() ? (an if so, why derby connection close command call
> > itself database;shutdown=true commande ?)
> > 
> > And a the very end of my application I do a derby shutdown
> > DriverManager.getConnection("jdbc:derby:cs;shutdown=true");
> > 
> > that's right ? :)
> 
> No, you need only shut down the database at the end of your application.
> Note that a derby shutdown is just a shutdown of all databases you have 
> opened.  If you just have a single database, a single shut down is enough.
> 

So if I call shutdown a the very of the application I should use Derby
shutdown to close all database (even if there is only one) ?
In fact, Derby shutdown do a checkpoint of all database that have been
opened during the JVM life. That's it ?