Yes, that's what I was thinking, but I didn't know if there was some automagic database migration.
Maybe a minor documentation update would suffice. IMHO, even if some database fields are not mandatory, it is generally bad practice not to migrate databases. You really don't want some people having one schema and other users having a different schema - it just makes for more consistency in deployment and less support issues, especially when dealing with ORM tools. Ken On Fri, Sep 19, 2008 at 1:50 PM, Wendy Smoak <[EMAIL PROTECTED]> wrote: > On Fri, Sep 19, 2008 at 10:44 AM, Ken Liu <[EMAIL PROTECTED]> wrote: > > Out of curiosity, how does Continuum handle the addition of new fields > when > > upgrading from 1.1 to 1.2? > > > > Does Continuum 1.2 automatically update the database schema at startup? I > > didn't see any documentation indicating that there is a migration script > > that needs to be run when upgrading. > > We've been tracking model changes here: > http://cwiki.apache.org/confluence/display/CONTINUUM/Model+Changes > > The 1.2 docs state that no upgrade tool is needed: > > http://people.apache.org/~olamy/staging-sites/continuum-1.2/docs/1.2/installation/upgrade.html<http://people.apache.org/%7Eolamy/staging-sites/continuum-1.2/docs/1.2/installation/upgrade.html> > > ...however, I see mention of some new *mandatory* fields on the wiki, > so I'm not certain. :( > > -- > Wendy >
