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 (athena.apache.org: local policy)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; format=flowed; charset=iso-8859-1;
 reply-type=original
Message-id: <000301c93901$6a840fc0$720411ac@martin>
Reply-to: martin stanik <martin.stanik@ecs-online.sk>
From: martin stanik <martin.stanik@ecs-online.sk>
To: derby-user@db.apache.org
Subject: should derby use addShutdownHook() out of box?
Date: Tue, 28 Oct 2008 14:30:58 +0100

hi,

I (silly boy) do not understand why derby engine needs to be shut down using
DriverManager.getConnection("jdbc:derby:;shutdown=true");

My application uses datasource, which is  _sometimes_  configured to use 
derby.
I do not like always execute the statement, as derby might be not in use and 
it could
cause loading derby classes.
I do not like idea to investigate my datasource if it does use derby or not.

Since 1.3 we have Runtime.addShutdownHook() - for me it looks like perfect 
solution
and derby should use it  by default after starting engine.

Am i wrong? Where i could found arguments?


thanks, martin