Re: Table Design for Hierarchical Data

From: Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com>
To: pgsql-sql(at)postgresql(dot)org
Cc: Yeb Havinga <yebhavinga(at)gmail(dot)com>
Subject: Re: Table Design for Hierarchical Data
Date: 2010-04-08 06:56:06
Message-ID: 201004080956.06446.achill@matrix.gatewaynet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

Στις Wednesday 07 April 2010 23:33:07 ο/η Yeb Havinga έγραψε:
> Achilleas Mantzios wrote:
> > Στις Wednesday 07 April 2010 11:06:44 ο/η Yeb Havinga έγραψε:
> >
> >> Achilleas Mantzios wrote:
> >>
> >>> You could also consider the genealogical approach, e.g.
> >>>
> >>>
> >>> The parents of any node to the root, i.e. the path of any node to the root are depicted as
> >>> parents[0] : immediate parent
> >>> parents[1] : immediate parent of the above parent
> >>>
> >>>
> >> What I have more than one parent?
> >>
> >
> > Then it is no longer neither a tree, nor a hierarchical structure, but rather a graph.
> > This a totally different problem.
> >
> My question was actually an attempt to point at the inability of what
> you call the 'genealogical approach' database design to store
> information of more than one parent.

Are you suggesting that we should change our definition of trees ADT, just because it does not
fit the mere detail that humans have two parents?
Or are you just suggesting that the "genealogical" term is inaccurate?

Take a look here: www.tetilab.com/roberto/pgsql/postgres-trees.pdf

>
> regards,
> Yeb Havinga
>
>

--
Achilleas Mantzios

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Yeb Havinga 2010-04-08 07:40:35 Re: Table Design for Hierarchical Data
Previous Message Yeb Havinga 2010-04-07 20:33:07 Re: Table Design for Hierarchical Data