This entire discussion is a great example of why all of WebObjects
should be open sourced. Just imagine how advanced WebObjects could
be. Look at how much activity there is in the open source Ruby on
Rails project. It's amazing.
We currently use the userInfo to store keys and values to support the
automatic generation of indexes (regular and compound) using the
PostgreSQL plug-in from Wonder. I guess whatever SQL generation
method is designed will have to take your index keys into
consideration and also be aware of each database's unique way of
generating indexes. I don't know if all databases use the same index
generation syntax, but maybe that's still something that needs to be
left up to a database specific plug-in of sorts. Or perhaps there
could be some sort of template mechanism built in to the new modeler
that can do substitution. E.g. "create index $indexName on $tableName
($columnName1, $columnName2, $...);" All the parts with the $ can be
substituted at SQL generation time but all the static parts could be
customized to each database's specific requirements. But alas perhaps
this isn't necessary. Just an idea.
Keep up the good work Mike. See you at WWDC.
____________________________________________________________________
Brendan Duddridge | CTO | 403-277-5591 x24 | brenda..lickspace.com
ClickSpace Interactive Inc.
Suite L100, 239 - 10th Ave. SE
Calgary, AB T2G 0V9
On Jul 19, 2006, at 8:13 AM, JR Ruggentaler wrote:
> Adding support for index and documentation in the model would be a
> big improvement over EOModeler in my opinion.
>
> J.R.
> -----Original Message-----
> From: Dov Rosenberg [mailto:dov.rosenber..onviveon.com]
> Sent: Wednesday, July 19, 2006 8:37 AM
> To: woproject-de..bjectstyle.org
> Subject: EOModeler Feature Request
>
> 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 - 10:42:11 EDT