db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yip Ng" <yipng...@gmail.com>
Subject Re: [jira] Commented: (DERBY-630) create trigger fails with null pointer exception
Date Thu, 12 Oct 2006 23:17:26 GMT
Thanks for the tip, Suresh.

On 10/12/06, Suresh Thalamati <suresh.thalamati@gmail.com> wrote:
>
> Hi Yip,
>
> I think by setting derby.database.allowPreReleaseUpgrade=true , in the
> derby.properties , you can upgrade from 10.2 to 10.3 (trunk)
>
> /suresh
>
> Yip Ng (JIRA) wrote:
> >     [
> http://issues.apache.org/jira/browse/DERBY-630?page=comments#action_12441875]
> >
> > Yip Ng commented on DERBY-630:
> > ------------------------------
> >
> > Hi Bryan.  I am glad that you brought this up.  In the current state of
> the trunk, the soft upgrade code that I put into the current patch will not
> get triggered since the release.properties file's beta property is set to
> true and the maint property has a value of 0 which indicates alpha.  Thus,
> the system will not allow an upgrade to occur.  i.e.:
> >
> > <snip>
> > ij version 10.3
> > ij> connect 'jdbc:derby:db102' user 'user1';
> > ERROR XJ040: Failed to start database 'db102', see the next exception
> for details.
> > ERROR XCW00: Unsupported upgrade from '10.2' to '10.3 beta'.
> > </snip>
> >
> > I am not sure what the next release will be, so I didn't modify the
> release.properties file.  However, I did run the soft upgrade test
> manually to verify my code changes are executed correctly.  What I did was:
> >
> > 1) Set the beta property to false and maint property to non-zero value
> (1000001, for example)
> >
> > 2) In order for the soft upgrade to get triggered, the data
> dictionary(dd) version (currently 140 for 10.2.1.6)
> > needs to  be incremented to a higher version number than the on-disk
> version.
> >
> > 3) Create the database in 10.2.1.6, this will have dd version of 140.
> >
> >
>

Mime
View raw message