Re: best practice for handling database schema changes

From: Michael Gentry (blacknex..mail.com)
Date: Thu Nov 30 2006 - 10:50:21 EST

  • Next message: Tobias SCHOESSLER: "best practice for handling database schema changes"

    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 <Tobias.Schoessle..nvienna.org> 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

    This archive was generated by hypermail 2.0.0 : Thu Nov 30 2006 - 10:50:59 EST