Re: two one-to-one relations between two tables
Chuck Hill <[email protected]> Fri, 01 Aug 2003 17:53:12 -0700
| Newsgroups | gmane.comp.web.webobjects.eof |
|---|---|
| Organization | Global Village Consulting, Inc. |
| Message-ID | <[email protected]> |
That should not be a problem. The Customer will need to have two foreign keys into Salesman, one for current and one for previous salesman. The currentSalesman relationship links customer.currentSalesmanFK to salesman.PK and the previousSalesman relationships links customer.previosuSalesmanFK to salesman.PK Chuck Ricardo Strausz wrote: > Hola tod@s! > > I was presented today with a modeling problem which is giving me rounds > on my head... > > Two tables: Customers and Salesmen > Each customer has associated two DIFFERENT salesman: current and previous. > The names of the salesmen are stored ONLY in the Salesmen table and I > need to report them, by customer... to flatten the atributes was the > first response, but.... > If I build a one-to-one relation from Customers to Salesmen (connecting > Customer.salesman to Salesmen.folio ---or ID if you prefere), EOModeler > prevents me to add another one-to-one relation to connect > Customer.previousSalesman to Salesmen.folio... > > I can understand why EOModeler does it, but I had not been able to > figure out a solution... > > I know, it's friday night, but hope someone will be able to help us with > this one. > > De antemano gracias, > > > Dino > http://homepage.mac.com/strausz > _______________________________________________ > webobjects-dev mailing list | [email protected] > Help/Unsubscribe/Archives: > http://www.lists.apple.com/mailman/listinfo/webobjects-dev > Do not post admin requests to the list. They will be ignored. -- Chuck Hill [email protected] Global Village Consulting Inc. http://www.global-village.net Progress is the mother of all problems. - G. K. Chesterton