I think I found a clean generic solution to the problem of updating
obscure dependencies between DB and Object mapping layers in the
Modeler. I wrote a prototype wrapping the whole Cayenne project tree
into an Ashwood graph (http://objectstyle.org/ashwood/), with graph
connections (aka "arcs") representing such dependencies. Any structural
project changes made in the Modeler are done via generic graph methods,
and Ashwood automagically updates all related pieces.
To make the long story short - this will be fixed. Not in the upcoming
Beta 2, but most likely in Beta 3. However the possibilities opened by
this change are much bigger than just fixing the model fragility. I can
think of a variety of filtered custom Modeler views, and maybe visual
entity graphs, who knows...
Andrus
On Jul 14, 2004, at 4:55 PM, Andrus Adamchik wrote:
> 2. Renaming DB Layer pieces.
>
> I am aware of the problem mentioned by Jürgen with renaming of the DB
> layer artifacts - basically it may require manual remapping of the
> affected object layer parts or using "Sync ObjEntity with DbEntity".
> The goal is to fix that while we are in beta.
>
> But please, pleASE, PLEASE, open bug reports when you encounter any
> such glitches! Tracking bugs in a project of such scale becomes a
> problem bigger than actually fixing them. Let us know and we'll fix it
> ;-)
This archive was generated by hypermail 2.0.0 : Wed Jul 21 2004 - 00:57:23 EDT