Re: Initial review of xslt with no limits patch - Mailing list pgsql-hackers

From David E. Wheeler
Subject Re: Initial review of xslt with no limits patch
Date
Msg-id 014683DB-6CA7-49E0-A884-98AACB064740@kineticode.com
Whole thread Raw
In response to Re: Initial review of xslt with no limits patch  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Initial review of xslt with no limits patch  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
On Aug 6, 2010, at 11:13 AM, Tom Lane wrote:

> That would work too, although I think it might be a bit harder to use
> than one alternating-name-and-value array, at least in some scenarios.
> You'd have to be careful that you got the values in the same order in
> both arrays, which'd be easy to botch.
>
> There might be other use-cases where two separate arrays are easier
> to use, but I'm not seeing one offhand.

Stuff like this makes me wish PostgreSQL had an ordered pair data type. Then you'd just have a function with `variadic
orderedpair` as the signature. 

I don't suppose anyone has implemented a data type like this…

Best,

David



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Review: Re: [PATCH] Re: Adding xpath_exists function
Next
From: Andres Freund
Date:
Subject: Re: Cost of AtEOXact_Buffers in --enable-cassert