Re: Horizontal Inheritance vs Abstract
Re: Horizontal Inheritance vs Abstract
- Subject: Re: Horizontal Inheritance vs Abstract
- From: Chuck Hill <email@hidden>
- Date: Tue, 6 Sep 2005 20:57:09 -0700
Hi Ian,
The answer is... it depends. Grin. For FrontBase, you need to have
the table there as that is what the unique key generator is
associated with. Other databases may need it for similar reasons.
If the database is using the EO_PK_TABLE to generate the keys then
this table really is superfluous.
Chuck
On Sep 6, 2005, at 8:51 PM, Ian Joyner wrote:
Perhaps I am not looking in the right place for the answer to this.
I have entities using horizontal inheritance where the parent
entity is abstract (because all the subclasses get their own copies
of attributes).
Now when I created the parent entity, I also gave it a table name
in EOModeler, which of course generates a table of that name.
However, since the entity is abstract the table is superfluous.
My question is: Is it alright to leave the table name blank so that
the table does not get generated for abstract entities? I don't
seem to be able to find this in the lists or in any books on EO and
horizontal inheritance.
Thanks
Ian Joyner
Sportstec
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40global-village.net
This email sent to email@hidden
--
Practical WebObjects - a book for intermediate WebObjects developers
who want to increase their overall knowledge of WebObjects, or those
who are trying to solve specific application development problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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