Hi Doug,

that shouldn't be a problem as long as the other entity does not have 
attributes that are marked as NOT NULL which would result in exceptions during 
save or fetch.

jw


Am 05.06.2012 um 16:29 schrieb doug andrews:

> In one model, I have two entities that reference the same table.
> One entity exposes attributes that the other does not.
> One entity has a custom class, the other's class is EOGenericRecord.
> Neither entity has a parent.
> 
> This is old code with a lot of lines, so removing one of the entities is not 
> an option.
> 
> Will this be a problem?
> Should one entity have the other as a parent?



 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to