Re: db Model and EOModel
Re: db Model and EOModel
- Subject: Re: db Model and EOModel
- From: Guido Neitzer <email@hidden>
- Date: Fri, 21 Mar 2008 22:39:34 -0600
On 21.03.2008, at 21:46, Gustavo Pizano wrote:
Ok so here it is my db model and my EOModel, what do you think? is
it good? the relations in EOModel? I dunno if i did it good in
EOModel based n the db design.
You have set some foreign keys to be class properties - you really
don't want that with EOF.
Attributes should be "camelCase" and not "camel_case". These will be
the Java class properties and should follow the Java naming conventions.
The m:n relationship is not really nicely modeled - use the
relationship inspector and give nicer (Java land!) names for the
relationships (shorter, clearer). Example: if a Person has a
speciality relationship that is a "to many" the relationship name
should be "specialities".
Person has a relationship "person_studyLevels" which is a to one but
is plural. It should be "studyLevel" or so to reflect the property.
I'm pretty sure, the "study level" is a lookup entity and you don't
want to have a person_id on it. Also the relationship in here is not
properly named.
That's just from a quick look. You should really be careful to model
that stuff correctly.
cug
--
http://www.event-s.net
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden