X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 1DFCCD1B4FD for ; Thu, 23 Oct 2003 11:41:04 +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 36576-02 for ; Thu, 23 Oct 2003 08:40:35 -0300 (ADT) Received: from trolak.mydnsbox2.com (ns1.mydnsbox2.com [207.44.142.118]) by svr1.postgresql.org (Postfix) with ESMTP id 7B348D1B50E for ; Thu, 23 Oct 2003 08:40:31 -0300 (ADT) Received: from dunslane.net (cpe-024-211-141-025.nc.rr.com [24.211.141.25]) (authenticated (0 bits)) by trolak.mydnsbox2.com (8.11.6/8.11.6) with ESMTP id h9NBYFX02938 for ; Thu, 23 Oct 2003 06:34:15 -0500 Message-ID: <3F97BE31.1030605@dunslane.net> Date: Thu, 23 Oct 2003 07:40:33 -0400 From: Andrew Dunstan User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4b) Gecko/20030508 X-Accept-Language: en-us, en MIME-Version: 1.0 To: PostgreSQL-development Subject: Re: is GiST still alive? References: <200310220438.h9M4cY232554@hosting.commandprompt.com> <200310221219.43179.josh@agliodbs.com> <60ptgpf175.fsf@dev6.int.libertyrms.info> <3F96FA03.6040009@dunslane.net> <3F97349A.5040300@familyhealth.com.au> In-Reply-To: <3F97349A.5040300@familyhealth.com.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/1075 X-Sequence-Number: 45757 Storing the XML text has problems - you have to parse it every time you want something - that has to cause a huge performance hit. I use XML a lot for all sorts of purposes, but it is appropriate for data transfer rather than data storage, IMNSHO. cheers andrew Christopher Kings-Lynne wrote: > Do this: > > 1. Create a new type called 'xml', based on text. > > 2. The xmlin function for that type will validate what you are > enterering is XML > > 3. Create new functions to implement XPath, SAX, etc. on the xml type. > > 4. Extend the contrib/ltree gist-based tree indexing scheme to work on > xml and hence the operations in no.3 above are really fast... > > Chris > > > Andrew Dunstan wrote: > >> Christopher Browne wrote: >> >>> But I think back to the XML generator I wrote for GnuCash; it has the >>> notion of building up a hierarchy of entities and attributes, each of >>> which is visible as an identifyable object of some sort. Mapping that >>> onto a set of PostgreSQL relations wouldn't work terribly well. >>> >>> >> >> *nod* I have tried this several times - it just doesn't work well, >> because the maps are too different. >> >> You could do something like this: >> . a table for each element type, fields being the attributes, plus >> the node id. >> . a table to tie everything together (parent_id, child_id, >> child_order, child_type). >> In theory you could even generate the DB schema from an XML schema >> and evaluate it with XPath-like expressions. >> >> But why put yourself to such bother? I have never found a good reason >> to do this sort of thing. >> >> cheers >> >> andrew >> >> >> ---------------------------(end of broadcast)--------------------------- >> TIP 7: don't forget to increase your free space map settings > > > > ---------------------------(end of broadcast)--------------------------- > TIP 7: don't forget to increase your free space map settings >