Mailing-List: contact dev-help@continuum.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@continuum.apache.org
Received-SPF: pass (athena.apache.org: domain of ken.liu@gmail.com designates
 209.85.198.246 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:references;
        b=Ascl9+9zSCU58PJjcWwdu0oi4je68BH60efhSeLzzgGUOketQ53ZQLB6WxnDRrzdgx
         +j501bvtoy96Ge4wG7keRjyfEfRjr9FujPQeWRZrGm48pEW7JhvsppL4H8nJkgfbzz+Y
         agT4KGcUqcgg4QnjBZcPho722Xa5zKZOrFQXA=
Message-ID: <748e286f0809191058s6adfde0dgfd25ea28aa215dd6@mail.gmail.com>
Date: Fri, 19 Sep 2008 13:58:42 -0400
From: "Ken Liu" <ken.liu@gmail.com>
To: dev@continuum.apache.org
Subject: Re: svn commit: r695183 - in /continuum/trunk:
 continuum-api/src/main/java/org/apache/continuum/dao/
 continuum-api/src/main/java/org/apache/maven/continuum/
 continuum-core/src/main/java/org/apache/maven/continuum/
 continuum-model/src/main/mdo/ contin
In-Reply-To: <adba96190809191050k4878d60bp81a9269bb783db44@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_38322_19251381.1221847122709"
References: <9948cb690809140940l18ead957u650fdb0946c5eb7@mail.gmail.com>
	 <10c62ca80809141629o5b848b95je500f07e9809f411@mail.gmail.com>
	 <CDEBDE8A-CB5C-4620-B7AA-3299726A88EF@apache.org>
	 <748e286f0809191044i56e56956n471e392c872bbdb5@mail.gmail.com>
	 <adba96190809191050k4878d60bp81a9269bb783db44@mail.gmail.com>

------=_Part_38322_19251381.1221847122709
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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 <wsmoak@gmail.com> wrote:

> On Fri, Sep 19, 2008 at 10:44 AM, Ken Liu <ken.liu@gmail.com> 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
>

------=_Part_38322_19251381.1221847122709--