Re: Nested Sets And Pedigrees

From: drop the numbers <Paul>
Date: Wed, 10 Apr 2002 20:45:42 GMT
Message-ID: <MPG.171e6f04a621015e9896db_at_news.easynews.com>

In article <3cb3f397$1_at_news.uia.ac.be>, hidders_at_uia.ua.ac.be says...
> "--CELKO--" <71062.1056_at_compuserve.com> wrote in message
> news:c0d87ec0.0204091405.2295590a_at_posting.google.com...
> >
> > Arkansas marriages? But it is the fact that each child has two, not
> > one, parents is the real sourc eof the problem.
>
> Was my proposal really that unclear?

        No, not unclear. :) It seems like a good idea.

        There are two issue that come to mind that I guess one would need to think through:

1. The first issue would become one of "knitting" back together the two trees properly for a pedigree drawing. First, you'd need another table for husband-wife pairs. I would assume the knitting would have to be done in code? Then, you'd need to resolve
2. What about 'sibling-of' problems? For example, part of the nested set for mother A would go to father A, and the rest to father B. Do you envisage this to be something else that application code would need to resolve?

        I guess I'm too new at such SQL complexity to immediately see if there are potential roadblocks that one might never get past. :) I was hoping for something simple like the nested set approach.

(Any opinions expressed are strictly mine only and not my employer's)

---

Paul Tiseo, Intermediate Systems Programmer Reply To: 123tiseo.paul_at_123mayo.edu (drop the numbers) Received on Wed Apr 10 2002 - 22:45:42 CEST