Jonathan,
I'd suggest sticking with the modeler a bit longer. Once you get over
some of the quirky things (with Swing apps in general) you'll find that
it's a very productive modeling tool.
General rule of thumb when starting from scratch....
1) Create all your DbEntities
- define all your DbAttributes (what you want your column names to be)
- define what DbAttributes are mandatory (little checkboxes)
- define which column(s) make up your primary key (little checkboxes)
2) Create all your DbRelationships
- map your DbEntities together (create reverse relationships)
3) Create all matching ObjEntities for each DbEntity
- add and map ObjAttributes to corresponding DbAttributes
Also check out "Sync ObjEntity with DbEntity" feature under the
"Project". It will help you avoid a lot of the stuff you'd normally
have to do in step three.
Cheers,
Eric
On Jul 14, 2004, at 11:01 AM, Jonathan Carlson wrote:
> Does anyone use the Cayenne Modeler for defining their data model?
>
> I've started defining a data model with it and it seems very sensitive
> to name and type changes. I'm thinking that maybe I should instead
> use a tool like http://druid.sf.net to define the database tables and
> then reverse engineer with the modeler. Is that what most people are
> doing?
>
> Thanks in advance,
>
> Jonathan
>
>
>
> ***********************************************************************
> **********
> This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they
> are addressed. If you have received this email in error please notify
> the system manager.
>
> Katun Corporation -- Celebrating 25 Years of Service
> www.katun.com
> ***********************************************************************
> **********
>
This archive was generated by hypermail 2.0.0 : Wed Jul 14 2004 - 13:45:53 EDT