db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tom_ <tom12...@web.de>
Subject Re: Failed to start database
Date Sat, 05 Jan 2008 17:42:29 GMT

It has to be set in the file derby.properties which has to be created. Now
the upgrade message has gone, but the exception with getCollationKey() is
shown again. I'm having a serious problem with this because I have to create
a release and am lacking of a stable version.


tom_ wrote:
> 
> Isn't the file service.properties in the database directory the right
> place for setting this property? I have also added "update=true" to the
> connection string.
> 
> 
> oysteing wrote:
>> 
>> tom_ wrote:
>>> I have tried with the latest bits/trunk, here the problem is an
>>> exception
>>> "upgrade from 10.3 to 10.4 is not supported".
>> 
>> Have you followed my advice about setting the 
>> derby.database.allowPreReleaseUpgrade property?
>> 
>> --
>> Øystein
>> 
>> 
>> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Failed-to-start-database-tp14561205p14636492.html
Sent from the Apache Derby Users mailing list archive at Nabble.com.


Mime
View raw message