An update on this feature...
Unfortunately it looks like too big of a change to incorporate into
1.1. I have this code developed in parallel to the main Cayenne tree,
and while it works pretty well, there is just too many small details to
test. So switching to this code can seriously destabilize the Modeler
and I decided against doing it now. So then I guess it will be released
in 1.2...
Andrus
On Jul 21, 2004, at 12:57 AM, Andrus Adamchik wrote:
> 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 : Tue Aug 31 2004 - 09:47:31 EDT