I think that the best idea would be to use a third table, something like
a Couples table, with a unique couple ID and two foreign keys into the
person table for each spouse respectively. This is similar to the
marriage ID concept, except with the requirement of a third table. This
might make things cleaner down the road (e.g. Cascading updates and
stored procedures). The Tom Jones - Norah Jones joke is also
appreciated.
Tyler
On Sun, 2003-08-10 at 18:00, ethan@ethanzimmerman.com wrote:
>
> - he's got a person table and an apartment table (it's a retirment home)
>
> - To cut to the chase I'm trying to find an elegant way to pair up two married
> people from the people table (i.e. Tom Jones and Nora Jones are a married couple
> and each exist as a seperate record in the people table) So I can then refer to
> the couple as a single entity
>
> - some ideas
> - I could give each person a marrige ID number and then pair up the numbers
> - I could use a Spouse ID field that links to the appropriate record in the
> person table (but that makes the pairing subroutine a bit harder)
>
>
> Any ideas about how I should do this?
-- Oh, and before people start telling me that RCU was successfully used in AIX/projectX/xxxx/etc, you have to realize that I don't give a rats *ss about the fact that there are OS's out there that are "more scalable".- Linus Torvalds
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 16:23:36 EDT