Hi Daniel,
I think I just had the same question here about a week ago.
Here's the answer that worked for me:
You can specify «1 to 1» relationship with Entity Modeler.
If the destination cannot be null, use the same id in the two tables.
-In Properties > Basic select : the cardinality «To One», your
destination, and add your primary keys.
-In Properties > Advanced select : for the source object, check
Propagates primary key and Owns Destination (if the destination object
cannot exist without an owner).
Jeff
On Apr 6, 2008, at 1:53 PM, Daniel DeCovnick wrote:
I've got a situation where I'm about 99% sure I should use a one-to-
one relationship. I've got about 100 attributes that can be
logically divided into 14 different categories. A single entity
(Note) would then have one of each of these categories (if modeled
as separate entities). There's no reuse possible of instances of the
categories.
Problem: The Create Relationship dialog in Entity Modeler won't let
me create a one-to-one relationship.
Question: Does this mean you can't have one-to-one relationships?
And if you can, how do you set one up?
Thanks,
Daniel
Daniel DeCovnick
danhd123 at mac dot com
Softyards Software
http://www.softyards.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/jeffandmonica%40mac.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
