After thinking about this one and Garry's index suggestion, I'm
thinking I should write things like this into userInfo, but not make
it visible to the users of the modeler. So when it loads in, we
would read these things out of userInfo and write them back out in
userInfo, but remove them from userInfo while you're using modeler
(basically just using userInfo for persistence). That way you can
get to these things, but it won't pollute the UI.
I have to do some "real" work today :) So I won't get back to EM
till tonight, but some of these would be cool to add in for WWDC.
ms
On Jul 19, 2006, at 9:36 AM, Dov Rosenberg wrote:
> I have been following the discussions on the Cayenne usage within
> the EOModeler with some interest. We have been using WO since 1997
> and recently started using Cayenne for some new projects. Cayenne
> is a nice product and fills some holes left open by EOF (i.e.
> Support for DB2, db connection pooling, etc). But I really don’t
> see why there should be any concern what technology is being used
> to provide a tool to build an EOModel as long as it works within
> your application.
>
> That being said, in addition to adding the ability to generate
> indexes for the model – it would be VERY helpful to provide an
> ability to capture column and table level comments/descriptions and
> a ready way to generate a data dictionary. Maintaining that kind of
> information inside the model would be perfect instead of having to
> keep the documentation separate.
>
>
> --
> Dov Rosenberg
> Inquira Inc
> 370 Centerpointe Circle, ste 1178
> Altamonte Springs, FL 32701
> (407) 339-1177 x 102
> (407) 339-6704 (fax)
> drosenber..nquira.com
> AOL IM: dovrosenberg
>
This archive was generated by hypermail 2.0.0 : Wed Jul 19 2006 - 09:47:23 EDT