X-Original-To: pgsql-chat-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 89426D1B4E4 for ; Thu, 23 Oct 2003 03:37:58 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 61009-02 for ; Thu, 23 Oct 2003 00:37:27 -0300 (ADT) Received: from linda-2.paradise.net.nz (bm-2a.paradise.net.nz [202.0.58.21]) by svr1.postgresql.org (Postfix) with ESMTP id 62A54D1B4EB for ; Thu, 23 Oct 2003 00:37:26 -0300 (ADT) Received: from smtp-1.paradise.net.nz (smtp-1b.paradise.net.nz [202.0.32.210]) by linda-2.paradise.net.nz (Paradise.net.nz) with ESMTP id <0HN600GPRY2CHU@linda-2.paradise.net.nz> for pgsql-chat@postgresql.org; Thu, 23 Oct 2003 16:37:24 +1300 (NZDT) Received: from dbc.co.nz (stl3.cl.paradise.net.nz [203.96.151.36]) by smtp-1.paradise.net.nz (Postfix) with ESMTP id 7AB938277B; Thu, 23 Oct 2003 16:37:24 +1300 (NZDT) Date: Thu, 23 Oct 2003 16:37:24 +1300 From: Kurt at DBC Subject: Re: [HACKERS] is GiST still alive? In-reply-to: To: Christopher Browne Cc: pgsql-chat@postgresql.org Message-id: <3F974CF4.90509@dbc.co.nz> Organization: Database Communications LTD. MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en-us, en User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20011022 Netscape6/6.2 References: <3F96FA03.6040009@dunslane.net> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/2 X-Sequence-Number: 15 Christopher Browne wrote: > No, "tables" wouldn't be the right way to do it. > > But it's going to be troubled, in any case, because of the > every-popular mixtures of: > a) Often weird declarations of what character sets are in use; > b) Pointers to other parts of a document; > c) What's a "database" going to consist of? One XML document? Or > many? And if many, then then how do you have a centralized > reference point to navigate from to find the document that you > want? > And "navigate" was a carefully chosen word; what you then have is > essentially a network database system, and have to then start making > up ways of describing queries. XQuery may be better than CODASYL of > yesteryear, but you're still left writing a lot of recursive code. > (Thus making those that understand the Lambda Nature more powerful...) > > At the end, do you have a "database?" Or just a set of documents? > It's hard to tell, a priori. > [Trimmed comments on utility of such features] transferred from pgsql-hackers to pgsql-chat. Coincidentally, just recently looked at Fongs "The design and implementation of the POSTGRES query optimizer2" (referenced in the Developers Guide) which implies that one of the initial goals of postquel and postgres was to handle similar structures : "The basic problem here is that the relational model is not well-suited for representing hierarchical relationships. As a solution, Stonebraker has proposed embedding queries within data fields and using these queries to express the hierarchical relationship between the corresponding tuple and information elsewhere in the database [STON84]. Using this idea, which POSTGRES supports, our complex object example is now represented as shown in figure 2.5. To retrieve information executed by the queries embedded within this data field, the user would issue the following query: execute (COBJECT.components) where COBJECT.coid = 1. Thus, n join queries reduce to a single execute query. In addition, users can selectively retrieve information linked through these hierarchies by nesting attributes" Go's around, comes around. Cheers, Kurt.