Re: Encoding materialized path in an atomic value.
- From: Wolfgang Riedel <wolfgang.riedel@xxxxxxxxxx>
- Date: Mon, 26 Sep 2005 12:17:03 +0200
David Cressey wrote:
>
> "Hugo Kornelis" <hugo@xxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:4eq8j1pvan8qnmo7sh8235eamtraqmae41@xxxxxxxxxx
> > On Fri, 23 Sep 2005 20:24:42 GMT, David Cressey wrote:
>
> > Maybe I'm missing something here? What would the code be for your
> > father's father's father's mother's father's mother? If I understand the
> > method correctly, the binary LSB-first notation would be 111010. And
> > that would also be 23 in decimal.
> >
> > >23 is, I think we will all agree "atomic" or "simple" enough so that it
> > >can be stored in a single value.
> >
> > Yeah. But in this case, it lacks unambiguity.
> >
> > Best, Hugo
> > --
>
> Hugo,
>
<snip>
If you do that, the ambiguity you mention disappears.
>
> Your parents become 2 and 3
> Your grandparents become 4 through 7,
> Your great grandparents become 8 through 15
> and so on.
<snip>
not so, you can be the offspring of the same person in more than one way.
The same person might even be present in different generations.
Otherwise everybody would have had some 2 ** 240000 grandgrand....parents a time
ago.
Wolfgang
.
- Follow-Ups:
- Re: Encoding materialized path in an atomic value.
- From: David Cressey
- Re: Encoding materialized path in an atomic value.
- References:
- Encoding materialized path in an atomic value.
- From: David Cressey
- Re: Encoding materialized path in an atomic value.
- From: Hugo Kornelis
- Re: Encoding materialized path in an atomic value.
- From: David Cressey
- Encoding materialized path in an atomic value.
- Prev by Date: Re: Database design, Keys and some other things
- Next by Date: Re: Database design, Keys and some other things
- Previous by thread: Re: Encoding materialized path in an atomic value.
- Next by thread: Re: Encoding materialized path in an atomic value.
- Index(es):
Relevant Pages
|