Re: Multiple EO classes inheriting from one abstract superclass?
Re: Multiple EO classes inheriting from one abstract superclass?
- Subject: Re: Multiple EO classes inheriting from one abstract superclass?
- From: Anjo Krank <email@hidden>
- Date: Fri, 7 Aug 2009 07:40:38 +0200
Am 06.08.2009 um 23:45 schrieb Chuck Hill:
I thought about this on the way home today, and I think this is a
case of while they appear to be subclasses, they are indeed
separate classes just with several attributes (all but the PK) in
that are the same. This is pretty odd from an OO-point-of-view, but
it is taking a view to coerce the actual tables into something
seemingly related in the first place.
It might make sense in pure-OO land, but EOF adds some restrictions
of its own. It really does need a consistent PK for the super and
all sub-classes.
Really? It may want it for the entities, but why the classes? You
should be able to set a superclass for the EO with some user info
setting so it will be properly generated. Or you don't generate it and
write the code yourself. But EOF shouldn't really have a problem with
it.
Cheers, Anjo
_______________________________________________
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