| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Mike Fowler <mike(at)mlfowler(dot)com>, "David E(dot) Wheeler" <david(at)kineticode(dot)com>, Anton <antonin(dot)houska(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Native XML |
| Date: | 2011-02-28 03:20:06 |
| Message-ID: | 4D6B1466.2000600@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 02/27/2011 10:07 PM, Tom Lane wrote:
> Andrew Dunstan<andrew(at)dunslane(dot)net> writes:
>> On 02/27/2011 03:06 PM, Tom Lane wrote:
>>> The case that I don't think we have any idea how to solve is
>>> http://archives.postgresql.org/pgsql-hackers/2010-02/msg02424.php
>> I'd forgotten about this. But as ugly as it is, I don't think it's
>> libxml2's fault.
> Well, strictly speaking it's libxslt's fault, no? But AFAIK those two
> things are a package.
>
>
No, I think the xpath implementation is from libxml2. But in any case, I
think the problem is in the whole design of the xpath_table function,
and not in the library used for running the xpath queries. i.e it's our
fault, and not the libraries. (mutters about workmen and tools)
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Treat | 2011-02-28 04:38:10 | Re: Problem with pg_upgrade (8.4 -> 9.0) due to ALTER DATABASE SET ROLE |
| Previous Message | Tom Lane | 2011-02-28 03:07:01 | Re: Native XML |