+1 here.. I filed a jira issue for this and scheduled it for 1.2. Please see http://jira.codehaus.org/browse/MRM-1001
Thanks, Deng On Tue, Nov 11, 2008 at 4:18 AM, Wendy Smoak <[EMAIL PROTECTED]> wrote: > I wrote about versioning the Continuum database a while back [1]. > Same thing here -- I think if the model changes, Archiva has to be > able to sense that it has been started with "old" data and either > upgrade itself or prompt the user to do it. (It seems like JPOX is > able to do some of this automatically?) > > [1] > http://www.nabble.com/Versioning-the-Continuum-database-ts18822595.html > > -- > Wendy > > On Mon, Nov 10, 2008 at 12:53 PM, Maria Odea Ching <[EMAIL PROTECTED]> > wrote: > > Looks like a problem with the upgrade :( There's a new repository > statistics > > table in 1.2-M1. > > I'll take a look at this problem and see if I can reproduce it.. > > > > Thanks for reporting this Dan :) > > > > -Deng > > > > On Tue, Nov 11, 2008 at 3:37 AM, Dan Tran <[EMAIL PROTECTED]> wrote: > > > >> sorry for the late notice, > >> > >> but when I try to to run 1.2-M1 on top my 1.1.3, my archiva does not > come > >> up > >> > >> here is the log > >> > >> 2008-11-10 11:31:21,480 [WrapperSimpleAppMain] ERROR JPOX.RDBMS - > >> Error thrown executing ALTER TABLE ARCHIVA_REPOSITORY_STATS ADD > >> TOTAL_PROJECT_COUNT BIGINT NOT NULL : In an ALTER TABLE statement, the > >> column 'TOTAL_PROJECT_COUNT' has been specified as NOT NULL and either > >> the DEFAULT clause was not specified or was specified as DEFAULT NULL. > >> ERROR 42601: In an ALTER TABLE statement, the column > ... >
