• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Limiting number of assignments in a many-to-many relationship
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Limiting number of assignments in a many-to-many relationship


  • Subject: Re: Limiting number of assignments in a many-to-many relationship
  • From: Denis Stanton <email@hidden>
  • Date: Tue, 13 Jan 2004 10:16:51 +1300

Steve

This seems like a standard one-to-many relationship. Very easy. Why are you thinking of implementing it as a many-to-many (much more difficult) and then artificially restricting one of the "manies" to a single item?

Surely you just need to add a foreign key to person, to point to organisation, and then connect the two by dragging a link in EOM to generate the "persons" relationship in organisation.


Denis On Tuesday, January 13, 2004, at 09:49 AM, 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.



Denis Stanton
email@hidden
Home:  +64 9 533 0391
mobile: +64 21 1433622
_______________________________________________
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.

  • Follow-Ups:
    • Re: Limiting number of assignments in a many-to-many relationship
      • From: Steve Sharman <email@hidden>
    • Re: Limiting number of assignments in a many-to-many relationship
      • From: Steve Sharman <email@hidden>
References: 
 >Limiting number of assignments in a many-to-many relationship (From: Steve Sharman <email@hidden>)

  • Prev by Date: Question on multi-language presentation
  • Next by Date: Re: Limiting number of assignments in a many-to-many relationship
  • Previous by thread: Limiting number of assignments in a many-to-many relationship
  • Next by thread: Re: Limiting number of assignments in a many-to-many relationship
  • Index(es):
    • Date
    • Thread