Hello Owen,
Are you joining on both TopicID and TrackingObjectID? Since that is
the primary key of TopicName, you must use both to uniquely identify
a row to get a to-one relationship.
To join on more than one attribute in EOModeler.app, first join on
one attribute (click Connect), then the other (and click Connect).
That warning message is a good one, and usually indicates something
is actually configured incorrectly in your model.
Regards,
Mark
On May 23, 2006, at 9:28 PM, Owen McKerrow wrote:
Hi All
We are trying to create a EOModel of a 3rd party database which I
cannot change.
When modelling the relationship between SubTopicName and TopicName
and then trying to save
we get the following error
Relationship TopicName in entity SubTopicName is a to-one
relationship, but its destination
attribute(s) does not match the primary key of the destination entity.
We think we have a problem because of the multiple primary keys in
the tables for Topic and SubTopicName
Can anyone please help provide a solution to this problem?
Tables and Primary key information and schema is attached.
<EOModelerProblem.doc>
Owen McKerrow
WebMaster, emlab
Ph : +61 02 4221 5517
http://emlab.uow.edu.au
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
