Re: EOModeler...
Re: EOModeler...
- Subject: Re: EOModeler...
- From: Ricardo Strausz <email@hidden>
- Date: Mon, 12 Jan 2004 13:09:15 -0600
Hola James!
On Jan 9, 2004, at 23:05, james cicenia wrote:
OK-
I have been throughly "righted" in my perspective. I think.
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?
There are basically 3 ways of modeling inheritance, one of them called
"single table mapping" which is more or less what you are suggesting...
however, this will not take your problem out; it has serious
disadventages (see "EOF Developer's Guide, pp. 124--134).
Or, do I make two tables out of the Project table?
I think this is better; try to split your data in an "object-centric"
way so it will be easer to mantain code, then this will give you some
outlines on how you most make your squema...
of course I am supposing here that you can change the squema.
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.
Think on EOModeler as an Object-Factory and FORGET that there is
relational-db behind.
-James
_______________________________________________
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.
_______________________________________________
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>) |