Re: xpath not a good replacement for xpath_string

From: James Pye <lists(at)jwp(dot)name>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: pgsql(at)mohawksoft(dot)com, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org, Kevin Grittner <kevin(dot)grittner(at)wicourts(dot)gov>
Subject: Re: xpath not a good replacement for xpath_string
Date: 2009-07-31 03:13:28
Message-ID: 7C63E0E0-AAAE-4EDB-8439-8729377F509C@jwp.name
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Jul 29, 2009, at 12:12 PM, Andrew Dunstan wrote:
> As I said upthread, I think we can easily provide some extra
> convenience functions which will do what you want. The only thing I
> was really arguing about was the function name for such a gadget.

+1.

"xpath_string" does seem unfortunate, but I'm not offended by it. =)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2009-07-31 04:59:10 Re: PATCH: make plpgsql IN args mutable (v1)
Previous Message Andrew Dunstan 2009-07-31 01:45:36 Re: PATCH: make plpgsql IN args mutable (v1)