Re: EOModeler...
Re: EOModeler...
- Subject: Re: EOModeler...
- From: Chuck Hill <email@hidden>
- Date: Fri, 09 Jan 2004 21:29:09 -0800
At 11:05 PM 09/01/2004 -0600, james cicenia wrote:
>OK-
>
>I have been throughly "righted" in my perspective. I think.
>
Grin.
>In my application I will have ProjectRequest objects and Project
>objects. These two objects "are" currently stored in the database
>as one Project table.
>
>Is the EOM way to make a Project entity subclass the ProjectRequest
>entity with both being set to the Project table in the database?
>
Yes. But I'm not sure the way you want. If you do this a row must be one
of Project or ProjectRequest (determined by contents of row at time of
fetch). It is an either / or thing, not an and / or thing.
>Or, do I make two tables out of the Project table?
If you are using inheritance this is not strictly required. If you are
refactoring your design, then at least two. I think you should be
splitting it into several tables.
>I think the answer to these questions will really help me truly
>understand EOModeler. Then I can go on to learn WebObjects to
actually build this web app.
>
It will make more sense if you approach them as a whole.
chuck
--
Chuck Hill email@hidden
Global Village Consulting Inc. http://www.global-village.net
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.
| References: | |
| | >EOModeler... (From: james cicenia <email@hidden>) |