Mailing-List: contact continuum-dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: continuum-dev@maven.apache.org
Received-SPF: neutral (herse.apache.org: local policy)
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <a43524d00704231200g5769deb0j3c24bc658647c02c@mail.gmail.com>
References: <541f12ca0704220418j6b09c0eal7907415f59725d6@mail.gmail.com>
 <1177243843.462b50c35dde0@webmail.jpox.org>
 <41E8693D-401E-4004-A0ED-7B31BF7685A2@apache.org>
 <541f12ca0704231157y3e903b8en9a8754abd97c59ce@mail.gmail.com>
 <a43524d00704231200g5769deb0j3c24bc658647c02c@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
Message-Id: <2A5036C7-9D42-498E-A889-9F8B920659CE@apache.org>
Content-Transfer-Encoding: quoted-printable
From: Brett Porter <brett@apache.org>
Subject: Re: DB schema migration
Date: Tue, 24 Apr 2007 02:21:10 +0200
To: continuum-dev@maven.apache.org

The problems Stephane has is because of the JPOX upgrade, not the =20
schema changes we've made.

I'm not saying it won't be possible to migrate from 1.0.3, it just =20
won't come out of the box (or necessarily be ready by the time the =20
release goes out).

- Brett

On 23/04/2007, at 9:00 PM, Jesse McConnell wrote:

> any remaining changes in 1.1 will at _most_ be additive in the form of
> a boolean value here or there for some improvement, there should be no
> more changing of column names or anything of that ilk...Those were
> taken care of in one fel swoop when we fixed things up to remove
> potential DB keyword conflicts
>
> jesse
>
> On 4/23/07, Stephane Nicoll <stephane.nicoll@gmail.com> wrote:
>> Can I be sure at least that the DB model won't change as from =20
>> alpha-1?
>> If so I can maybe drop completely my database and recreate my
>> projects.
>>
>> Thanks,
>> St=E9phane
>>
>> On 4/23/07, Brett Porter <brett@apache.org> wrote:
>> > This was one of the things I was going to try and have done before
>> > alpha-1 - I just forgot.
>> >
>> > Erik - the problem in upgrading is the changes in private tables
>> > between versions of jpox that we hadn't given explicit names to. =20=

>> We'd
>> > probably appreciate most help in future proofing our jpox use a bit
>> > more in case it's internal schema changes again.
>> >
>> > I already have the tools to do an xml export of the old tables, it
>> > just needs to somehow be set to run in dump mode using the old =20
>> jpox,
>> > and import using the new one. I'll look at that during ApacheCon, I
>> > think. If anyone else wants to take the task while I'm on holidays,
>> > let me know... we should also make the tool work with 1.0.3 =20
>> databases
>> > if possible.
>> >
>> > This is definitely one for the release notes, btw. alpha-1 will not
>> > work with 1.0.3 (or earlier 1.1 snapshot) databases.
>> >
>> > - Brett
>> >
>> > On 22/04/2007, at 2:10 PM, Erik Bengtson wrote:
>> >
>> > > If you guys need some tooling from JPOX, let me know and I could
>> > > plan to
>> > > implement some kind of "export" to XML, and "import" from XML. In
>> > > between
>> > > export/import you could apply Xqueries to transform data to match
>> > > the new
>> > > schema
>> > >
>> > > Quoting Stephane Nicoll <stephane.nicoll@gmail.com>:
>> > >
>> > >> Hi,
>> > >>
>> > >> I'm currently running a 1.1-SNAPSHOT from February which runs ok
>> > >> except a few minor issues. I'd like to upgrade to 1.1 alpha 1 =20=

>> as soon
>> > >> as it's out to provide feedback & co.
>> > >>
>> > >> Last time I tried to upgrade, I had to revert because the model
>> > >> schema
>> > >> has changed and it was really difficult to update my existing
>> > >> data. Is
>> > >> there something scheduled for alpha1 regarding this (at least a
>> > >> manual
>> > >> procedure to upgrade my schema if necessary).
>> > >>
>> > >> Thanks,
>> > >> St=E9phane
>> > >>
>> > >
>> > >
>> >
>>
>
>
> --=20
> jesse mcconnell
> jesse.mcconnell@gmail.com