On 06.04.2008, at 12:53, 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?
In WebObjects a "normal" 1:1 relationship is modeled with joining on
the primary keys and have the "master" entity propagate its pk to the
"slave". As soon as you create a master entity you'll get the other
end created automatically, so do not create another one!
If you don't want that, you need to model it yourself, e.g. with a 1:n
and cover methods to make the to n part a to 1 part.
cug
--
http://www.event-s.net
_______________________________________________
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]
