Re: DbGenerator vs. MergeContext

From: Andrus Adamchik (andru..bjectstyle.org)
Date: Fri Aug 22 2008 - 08:25:06 EDT

  • Next message: Andrus Adamchik: "Re: Original value of a property"

    On Aug 22, 2008, at 3:07 PM, Tore Halset wrote:

    > On Aug 22, 2008, at 13:36, Andrus Adamchik wrote:
    >
    >> Interesting... I am not using either for anything complex lately,
    >> preferring manual SQL scripts executed with dbpatch Ant task, so I
    >> am a bit out of the loop.
    >
    > The sql-scripts is a very solid way to work, but some people would
    > probably prefer the ease of the modeler for such tasks. The merger
    > is also very good for verifying that your model and database is in
    > sync.

    Totally agree. I just posted that to explain my own ignorance :-)

    >> I would also love to have less redundancy and drop DbGenerator at a
    >> point when there is a complete and more powerful replacement.
    >
    > Merge call DbGenerator where DbGenerator has the needed
    > functionality. The reason for this is to save code and testing. It
    > could easily be refactored when we are happy with the merger.

    Excellent. I'll keep that in mind.

    Andrus



    This archive was generated by hypermail 2.0.0 : Fri Aug 22 2008 - 08:25:38 EDT