Mailing-List: contact user-help@cayenne.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cayenne.apache.org
MIME-Version: 1.0
In-Reply-To: <DA3E4329-D6D1-4A90-8F4C-CC3C4D4726AC@karlmenn.is>
References: <DA3E4329-D6D1-4A90-8F4C-CC3C4D4726AC@karlmenn.is>
From: Michael Gentry <mgentry@masslight.net>
Date: Thu, 9 Feb 2017 10:15:23 -0500
Message-ID: <CAA-upzoF64xbiZeFrtEzkARB3pNdd2HzrqVg1M=X-6HNAVssdQ@mail.gmail.com>
Subject: Re: Cayenne and migrations
To: Cayenne Users <user@cayenne.apache.org>
Content-Type: multipart/alternative; boundary=001a1148e73274eba605481a74c6
archived-at: Thu, 09 Feb 2017 15:15:54 -0000

--001a1148e73274eba605481a74c6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Hugi,

We manage schema changes outside of Cayenne using Flyway (could also use
Liquibase).  Any schema changes we make are updated by hand in Cayenne
Modeler.  This works fairly well for us and fits in with our automated
builds/etc.  Perhaps not the answer you were looking for, though!

mrg


On Thu, Feb 9, 2017 at 9:21 AM, Hugi Thordarson <hugi@karlmenn.is> wrote:

> Hi all.
> In EOF/WOnder we have the most swesome ERXMigrations to manage changes in
> the data model between versions, i.e. upgrades of the schema (and
> downgrades, if applicable).
>
> I see that some years ago there was discussion of an API to handle this i=
n
> Cayenne ( http://svn.apache.org/repos/asf/cayenne/sandbox/cayenne-
> migrations/ ). but how=E2=80=99s the situation today? Is there something =
in/for
> Cayenne to do this, and if not, what tools are people using to manage
> versioning of their DB schemas?
>
> Cheers,
> - hugi

--001a1148e73274eba605481a74c6--