From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | John Gray <jgray(at)beansindustry(dot)co(dot)uk> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Re: Re: Storing XML in PostgreSQL |
Date: | 2001-07-26 21:28:55 |
Message-ID: | 200107262128.f6QLSuW05171@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Should we add this to /contrib?
> I've packaged up what I've done so far and you can find it at
> http://www.cabbage.uklinux.net/pgxml.tar.gz
>
> The TODO file included indicates what still remains to be done (a lot!).
>
> In particular, it would be good to implement more of the XPath grammar.
> However, once we get into the realm of more complex paths there becomes a
> question about optimisation of XPath selection. If the documents are
> pre-parsed, then XPath query elements can be rewritten as SQL queries and
> you get the optimisation of the planner on your side.
>
> I'd like to stick with the current solution if possible, because I think
> it delivers a very simple interface to the user and is (code-wise) also
> very straightforward. Maybe less efficient queries are a penalty worth paying?
>
> Any thoughts?
>
> Regards
>
> John
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2001-07-26 21:38:23 | Re: Bad timestamp external representation |
Previous Message | Joel Burton | 2001-07-26 20:37:06 | RE: LIBPQ on Windows and large Queries |