Primary key generation need to be observed to ensure no duplication of keys
happened in the same table. Since eo primary key table is using the table
name, it should be fine, too.
----- Original Message -----
From: "Johann Werner" <[email protected]>
To: "doug andrews" <[email protected]>
Cc: "WebObjects-Dev Mailing List List" <[email protected]>
Sent: Tuesday, June 05, 2012 10:56 PM
Subject: Re: EOEntity question.
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/chng34%40gmail.com
This email sent to [email protected]
_______________________________________________
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]
