That's a good one. I wonder if we should adopt something like that as
a Cayenne extension and use for things like prefs DB versioning in
the Modeler?
Andrus
On Dec 1, 2006, at 4:56 PM, Michael Gentry wrote:
I found this yesterday (although I haven't read it all yet):
http://www.stepwise.com/Articles/2005/DBChanges/index.html
Not sure if it'll be helpful, but it looks similar to some ideas I had
been pondering in the past.
/dev/mrg
On 11/30/06, Michael Gentry <[EMAIL PROTECTED]> wrote:
Currently you have to manually merge the changes just as you states.
I should probably make an FAQ for this ...
Thanks,
/dev/mrg
On 11/30/06, Tobias SCHOESSLER <[EMAIL PROTECTED]>
wrote:
>
> hi,
> What is the best practice for handling changes to the database
schema once a
> cayenne mapping was created?
> We use the 'reverse engineer from database' feature to create an
initial
> mapping. But then we usually have to do manual changes like map
some pks,
> add flattened relationships, etc.
> If then the database schema needs to be changed we usually have
a problem as
> 'reverse engineer from database' overwrites everything. There
seems to be
> the possibility to replace only selected tables but if you do
this the
> relationships are messed up. Is there a way to merge the
changes with the
> current model/mapping?
>
> thanks
>
> Tobias
