Re: Limiting number of assignments in a many-to-many relationship
Re: Limiting number of assignments in a many-to-many relationship
- Subject: Re: Limiting number of assignments in a many-to-many relationship
- From: Ricardo Strausz <email@hidden>
- Date: Mon, 12 Jan 2004 15:24:15 -0600
Your relation most be organisation<-->>person
instead of a many-to-many... or did I missed something?
On Jan 12, 2004, at 14:49, Steve Sharman wrote:
Happy New Year to all on the list.
I have a fairly simple question. In my application, I've implemented a
many to many relationship between two objects person and position -
with the obvious implication that each person may be assigned to one
or more position. I want to implement a similar relationship to
reflect the situation:
- There are many persons
- There are many organisations
- Many persons can be assigned to an organisation
- A person can be assigned to one and only one organisation
The way that I thought of approaching this was to implement a
many-to-many relationship in the usual way between person and
organisation, but implement a restriction at the Java level that would
ensure that a given person was assigned to only one organisation at a
time. Is this the best way to approach this requirement, and does
anyone have any pointers as to how it can be most efficiently
implemented?
Thanks in advance for your advice,
-- Steve
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.