db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Evan Leonard <evan.leon...@gmail.com>
Subject Re: Hard upgrade failing?
Date Tue, 02 Jun 2009 20:32:14 GMT

Thank you. I've implemented the plan below and it works well.

I agree that the requirement to have "upgrade=true" be on the first  
connection to a db be added to the documentation. Perhaps also include  
this trick about shutting down the db first to be able to upgrade the  
db in a single jvm instance that's already been connected to the db.

Thank everyone for your help.


On Jun 2, 2009, at 10:07 AM, Kathey Marsden wrote:

> Evan Leonard wrote:
>>  So for my scenario does it sound like this would work:
>> 1. startup application
>> 2. use softupgrade connection to determine database schema version
>> 3. user confirms upgrade via UI
>> 4. issue db shutdown connection
>> 5. issue db upgrade connection
>> 6. continue on using the application with the upgraded database
>> This would all be in one JVM instance, without ever restarting the  
>> JVM.  Anyone know of a reason this won't work?
> That sounds like a good plan, but just remember that your existing  
> connections that were established before shutdown will no longer be  
> usable and you will have to make new ones.
> Kathey

View raw message