when merging branches that both contain a
> schema update, you have to first rename your own migration to a higher
> number to keep them in sequence. This is easy to do, but I could imagine a
> more elegant way to manage the order of migrations to execute.
>
> As I understand, John's implem
This is easy to do, but I could imagine a more
elegant way to manage the order of migrations to execute.
As I understand, John's implementation is very much like this, right?
Maik
> Am 09.02.2017 um 23:17 schrieb John Huss <johnth...@gmail.com>:
>
>> Can someone please explain the
any object naming discrepancies, map custom value
> objects, map inheritance.
> 4. Run cgen to sync Java classes from Cayenne model
> 5. Rinse and repeat.
>
> Can someone please explain the workflow with ERX|cayenne migrations? What are
> the advantages over the approach
> Can someone please explain the workflow with ERX|cayenne migrations? What
are the advantages over the approach above? Does it handle data migrations
or only the schema?
Mainly schema migrations.
I think the advantages are:
1) Cross-database support from a single representation. So you can
in bootique-liquibase / bootique-flyway).
> 2. Run cdbimport from Maven/Ant/Gradle to sync Cayenne model from DB.
> 3. In the modeler fix any object naming discrepancies, map custom value
> objects, map inheritance.
> 4. Run cgen to sync Java classes from Cayenne model
> 5. Rinse and
cdbimport from Maven/Ant/Gradle to sync Cayenne model from DB.
3. In the modeler fix any object naming discrepancies, map custom value
objects, map inheritance.
4. Run cgen to sync Java classes from Cayenne model
5. Rinse and repeat.
Can someone please explain the workflow with ERX|cayenne migrat
s your current work public or is the most
> recent
> >> public work in the SVN-repo I mentioned?
> >>
> >> Cheers,
> >> - hugi
> >>
> >>
> >>> On 9. feb. 2017, at 15:36, John Huss <johnth...@gmail.com> wrote:
> >>>
> >
>> - hugi
>>
>>
>>> On 9. feb. 2017, at 15:36, John Huss <johnth...@gmail.com> wrote:
>>>
>>> I'm developing and using cayenne-migrations. It works fine for me and
>> has a
>>> very similar approach to ERXMigrations. I don't think
ing. Is your current work public or is the most recent
> public work in the SVN-repo I mentioned?
>
> Cheers,
> - hugi
>
>
> > On 9. feb. 2017, at 15:36, John Huss <johnth...@gmail.com> wrote:
> >
> > I'm developing and using cayenne-migrations. It w
Hi John,
that’s very interesting. Is your current work public or is the most recent
public work in the SVN-repo I mentioned?
Cheers,
- hugi
> On 9. feb. 2017, at 15:36, John Huss <johnth...@gmail.com> wrote:
>
> I'm developing and using cayenne-migrations. It works fine
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 in
>>
to be able to run Flyway migrations for us.
On Thu, Feb 9, 2017 at 10:36 AM, John Huss <johnth...@gmail.com> wrote:
> I'm developing and using cayenne-migrations. It works fine for me and has a
> very similar approach to ERXMigrations. I don't think others are using it
>
I'm developing and using cayenne-migrations. It works fine for me and has a
very similar approach to ERXMigrations. I don't think others are using it
though. It has the advantage of being able to auto-generate the migration
code from your cayenne model (DataMap), where I think the others require
see that some years ago there was discussion of an API to handle this in
> Cayenne ( http://svn.apache.org/repos/asf/cayenne/sandbox/cayenne-
> migrations/ ). but how’s the situation today? Is there something in/for
> Cayenne to do this, and if not, what tools are people using to manage
> versio
/cayenne/sandbox/cayenne-migrations/
). but how’s 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
15 matches
Mail list logo
