| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 15:36:51 |
| Message-ID: | AANLkTinhwx7=xhJoXpqH5hGuDrSarP1DV7ZzLkuFzNX1@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Feb 27, 2011 at 10:20 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> 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)
Yeah, I think the problem is that we picked a poor definition for the
xpath_table() function. That poor definition will be equally capable
of causing us headaches on top of any other implementation.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2011-02-28 15:40:01 | Re: Native XML |
| Previous Message | Tom Lane | 2011-02-28 15:30:18 | Re: Native XML |