db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chux <chu...@gmail.com>
Subject Re: When to shut down a database
Date Tue, 08 Apr 2014 09:00:56 GMT
Hey Dag,

Thanks for your insight.

I'm using this as an embedded DB in a Java FX desktop application. This is
a dumb question but would you recommend shutting down the database ever
after a transaction? Like after you create a record then you shut it down
after commit.


On Tue, Apr 8, 2014 at 12:32 AM, Dag H. Wanvik <dag.wanvik@oracle.com>wrote:

> On 06. april 2014 21:02, George Toma wrote:
>  Hi Chux,
>  In my opinion  the example from  app.  referred at commit the
> transaction OR close the connection ( a connection could be transacted too
> ), and not to shutdown the db. If the business rule specifies that the db.
> needs to be shutdown when the app. is shutdown, then so be it.
>  Normally the db is not shutdown, not even when the app is down.
> This is true for a client/server application. For use with embedded Derby,
> one would normally close down the database (and the database engine) before
> exiting the application. If one neglects to do so,
> one would see longer start-up times as Dyre indicated.
> Thanks,
> Dag
>  Cheers,
> George
>    On Sunday, April 6, 2014 7:14 PM, Chux <chux18@gmail.com><chux18@gmail.com>wrote:
>   Hello guys,
>  I read in a sample app that you've got to shutdown a database. I was
> just confused if you need to shut it down on every connection transaction
> or just shut it down on application close, in my case a desktop applicaiton.
>  Best,
> Chux

View raw message