> I think, the success of the Cayenne (and Modeler) depends
> to great degree on
> how smart is the reverse engineering step - the smarter it
> is, the less
> manual work has the user to do, so the greater the user
> satisfaction is.
I was trying Cayenne only because it has Cayenne Modeler(the reverse engineering menu item in 99% of the time).
> With scenarios of over 50 tables, manual intervention is
> simply a pain (from
> what I experienced so far :( ).
Now imagine what a pain in the back is when there are more than 180 tables :).
> > I'll get to CAY-1197 someday
> > and I'll set up a simple project in ant.
I'm interested in testing the ANT version too.
> I think however that to the same category of "smart reverse
> enginnering"
> should be these too:
> #1. https://issues.apache.org/jira/browse/CAY-154
> (better said the UI independent code - i.e. to detect
> automatically
> many2many and flattern where appropiate - if a setting for
> this is active)
> #2. https://issues.apache.org/jira/browse/CAY-400
> (to be able to get the comments from the DB attached to the
> object and DB
> entites)
> #3. https://issues.apache.org/jira/browse/CAY-209
> #4. https://issues.apache.org/jira/browse/CAY-850
> (or something similar - i.e. where there's a "name
> matching" but no concrete
> foreign key, to add a single directed relationship.
> E.g. many tables have
> "created_by_user_id", but no FK to the user)
> #5 Singularize of table names (if a setting is active)
#6. No existing FKs support
Please add an option to reverse engineer databases that don't
have foreign keys defined at all (this was discussed on the mailing lists:
many applications that come from Rails and similar web2.0 frameworks don't use FKs at all).
There should be field exclusion pattern however from this: e.g. "update%" or "create%" since those fields should have relationship in only one direction; because of -> #4
thanks,
Joseph
This archive was generated by hypermail 2.0.0 : Sun Apr 12 2009 - 12:43:40 EDT