cayenne-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Musall Maik <>
Subject Re: EOModel importer testing
Date Wed, 03 Aug 2016 19:27:38 GMT
Hi John,

I tried the reverse-engineering first, but as the database is case insensitive regarding names,
almost all entities and attributes came out without the camel casing that I use in the project.
Correcting that by hand for 169 entities with a huge number of attributes isn't an option,
so I tried the EOModel import. I only use two enum prototypes, both of which aren't Wonder
prototypes, so that left far less stuff to clean up.

There's still a bunch of details to fix, like TEXT columns (postgresql clobs) ending up as
varchar with no length, the parser not being able to cope with unicode umlauts in documentation
(similar to CAY-1291 which is also still unsolved), and more.


> Am 03.08.2016 um 20:57 schrieb John Huss <>:
> A pull request is preferred now.
> The biggest problem with the importer that I recall was that it was
> completely unaware of prototypes (ERPrototypes) so that basically made it
> worthless for me.  Are you having that problem?  Reverse-engineering from
> the database itself can work well as an alternative if your names use
> underscores.
> John
> On Wed, Aug 3, 2016 at 1:53 PM Musall Maik <> wrote:
>> Hi all,
>> I've got a rather large project to migrate from EOF to Cayenne, and in
>> order to eliminate the manual cleanup steps I'd have to do after each
>> conversion attempt until I'm ready for the final run, I thought I could
>> have a look and try to improve the EOModel importer instead of wasting time
>> fiddling with my one project.
>> To that end, what is the usual procedure to test changes made against the
>> modeler? Can I run it from within Eclipse? Or do I need to mvn install
>> every time I changed something? (Note that I'm new to both Cayenne and
>> Maven.)
>> How am I supposed to contribute the changes? Pull request against the
>> github mirror? The website [1] suggest submitting a patch, but that feels
>> so old-school, and the website still explains how to create a patch with
>> subversion, so I guess that's no longer up to date anyway?
>> Thanks
>> Maik
>> [1]

View raw message