Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 3A1FC6326E8 for ; Thu, 8 Apr 2010 04:40:45 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 44153-02 for ; Thu, 8 Apr 2010 07:40:34 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-ew0-f210.google.com (mail-ew0-f210.google.com [209.85.219.210]) by mail.postgresql.org (Postfix) with ESMTP id 64BF763435E for ; Thu, 8 Apr 2010 04:40:34 -0300 (ADT) Received: by ewy2 with SMTP id 2so939635ewy.16 for ; Thu, 08 Apr 2010 00:40:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=4FX7Div20kPxGUOmvoOYJSSv+Dytmo2R6YiRQ4hNyRg=; b=tuAKwdEjDYgh4T7aYBfwgpf0L5C/n/H0Ns2QLSN/pSL4oymGOnpZyG2hx7KO1m855P TaCnvohnbdyhch5Qo0Gl8TNm1i8EIxdbynXPNI5NP/tFDwfEPJqukZTl6dapPQz7tTas n3Y12/a3mIo1TSkl/eLiXR/85g1km3t3a+s7Y= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=drCAF1zhnV1refXKBqUqTgP21jNTuLL+H+8uJ7QkeT5I3Qfrxnc4mmRAlgLz+ATR5N lzPTRG2PWnbm3PHF3EMX+QK82Do7UnP9SpJf12Dm+z51fn16tHPekKonozPymkATJrgr jaAj1Tk9pBotWt0UQAfS2wDzAozt3JEXy0Lqs= Received: by 10.213.25.71 with SMTP id y7mr6037713ebb.54.1270712432092; Thu, 08 Apr 2010 00:40:32 -0700 (PDT) Received: from [0.0.0.0] (5357DA75.cable.casema.nl [83.87.218.117]) by mx.google.com with ESMTPS id 13sm8457975ewy.1.2010.04.08.00.40.30 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 08 Apr 2010 00:40:31 -0700 (PDT) Message-ID: <4BBD8873.5040003@gmail.com> Date: Thu, 08 Apr 2010 09:40:35 +0200 From: Yeb Havinga User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: Achilleas Mantzios CC: pgsql-sql@postgresql.org Subject: Re: Table Design for Hierarchical Data References: <201004071139.42140.achill@matrix.gatewaynet.com> <4BBCEC03.3050100@gmail.com> <201004080956.06446.achill@matrix.gatewaynet.com> In-Reply-To: <201004080956.06446.achill@matrix.gatewaynet.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=-10 required=5 tests=BAYES_50=0.001 X-Spam-Level: X-Archive-Number: 201004/26 X-Sequence-Number: 33953 Achilleas Mantzios wrote: > Στις 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? > The latter, but rethinking it, why would genealogical be a bad word when applied to graph algorithm 'stuff' when words like parent, child, ancestor, sibling are common use. When I read 'genealogical' I had only the connotation 'family relations' in mind. I suspect that if looking at the definition of the word genealogy alone, it could very well include the study of single parent transitive relationships. However, not exclusively, so yes, IMHO something called the genealogical approach should not preclude polyhierarchies. regards Yeb Havinga