You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@continuum.apache.org by Wendy Smoak <ws...@gmail.com> on 2008/08/05 02:43:16 UTC
Versioning the Continuum database
Is there currently any way that Continuum could know that it has been
started up with an old/incompatible database?
In my perfect world, Continuum would sense this and at least politely
refuse to start with an informative message. Preferably it would
offer to convert the data for me.
The experience I had recently upgrading OmniFocus to the new 1.1 Beta
version was, imo, how an upgrade should work. It asked if I wanted to
convert and warned me that there was no going back, then made a backup
of the existing data and did the conversion. A similar concept is
described in "Release It!" [1].
Any thoughts on what it would take to make this happen?
[1] http://www.pragprog.com/titles/mnee/release-it
--
Wendy
Re: Versioning the Continuum database
Posted by Dan Tran <da...@gmail.com>.
and now MOJO http://mojo.codehaus.org/dbupgrade/dbupgrade-maven-plugin/
On Mon, Aug 18, 2008 at 2:32 AM, Emmanuel Venisse
<em...@gmail.com> wrote:
> An other tool: http://code.google.com/p/agimatec-tools/
>
> Emmanuel
>
> On Tue, Aug 5, 2008 at 5:17 AM, Dan Tran <da...@gmail.com> wrote:
>
>> I am using something similar to http://code.google.com/p/dbmigrate/
>>
>> which allow us freely change database schema incrementally.
>>
>> -D
>>
>> On Mon, Aug 4, 2008 at 5:43 PM, Wendy Smoak <ws...@gmail.com> wrote:
>> > Is there currently any way that Continuum could know that it has been
>> > started up with an old/incompatible database?
>> >
>> > In my perfect world, Continuum would sense this and at least politely
>> > refuse to start with an informative message. Preferably it would
>> > offer to convert the data for me.
>> >
>> > The experience I had recently upgrading OmniFocus to the new 1.1 Beta
>> > version was, imo, how an upgrade should work. It asked if I wanted to
>> > convert and warned me that there was no going back, then made a backup
>> > of the existing data and did the conversion. A similar concept is
>> > described in "Release It!" [1].
>> >
>> > Any thoughts on what it would take to make this happen?
>> >
>> > [1] http://www.pragprog.com/titles/mnee/release-it
>> >
>> > --
>> > Wendy
>> >
>>
>
Re: Versioning the Continuum database
Posted by Emmanuel Venisse <em...@gmail.com>.
An other tool: http://code.google.com/p/agimatec-tools/
Emmanuel
On Tue, Aug 5, 2008 at 5:17 AM, Dan Tran <da...@gmail.com> wrote:
> I am using something similar to http://code.google.com/p/dbmigrate/
>
> which allow us freely change database schema incrementally.
>
> -D
>
> On Mon, Aug 4, 2008 at 5:43 PM, Wendy Smoak <ws...@gmail.com> wrote:
> > Is there currently any way that Continuum could know that it has been
> > started up with an old/incompatible database?
> >
> > In my perfect world, Continuum would sense this and at least politely
> > refuse to start with an informative message. Preferably it would
> > offer to convert the data for me.
> >
> > The experience I had recently upgrading OmniFocus to the new 1.1 Beta
> > version was, imo, how an upgrade should work. It asked if I wanted to
> > convert and warned me that there was no going back, then made a backup
> > of the existing data and did the conversion. A similar concept is
> > described in "Release It!" [1].
> >
> > Any thoughts on what it would take to make this happen?
> >
> > [1] http://www.pragprog.com/titles/mnee/release-it
> >
> > --
> > Wendy
> >
>
Re: Versioning the Continuum database
Posted by Dan Tran <da...@gmail.com>.
I am using something similar to http://code.google.com/p/dbmigrate/
which allow us freely change database schema incrementally.
-D
On Mon, Aug 4, 2008 at 5:43 PM, Wendy Smoak <ws...@gmail.com> wrote:
> Is there currently any way that Continuum could know that it has been
> started up with an old/incompatible database?
>
> In my perfect world, Continuum would sense this and at least politely
> refuse to start with an informative message. Preferably it would
> offer to convert the data for me.
>
> The experience I had recently upgrading OmniFocus to the new 1.1 Beta
> version was, imo, how an upgrade should work. It asked if I wanted to
> convert and warned me that there was no going back, then made a backup
> of the existing data and did the conversion. A similar concept is
> described in "Release It!" [1].
>
> Any thoughts on what it would take to make this happen?
>
> [1] http://www.pragprog.com/titles/mnee/release-it
>
> --
> Wendy
>