Re: array_map not SQL accessible?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: array_map not SQL accessible?
Date: 2009-01-30 18:17:47
Message-ID: 26397.1233339467@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> I'm wondering why don't we expose the array_map() function to the SQL
> level.

It requires some notion of "reference to function", which doesn't really
exist in SQL. (Please don't say you're going to pass it a function
OID.)

> As it happens, I need to use it in the pg_dump support for TOAST
> reloptions.

Maybe something involving
ARRAY(SELECT foo(x) FROM UNNEST(arrayvariable) x)

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2009-01-30 18:35:48 Re: array_map not SQL accessible?
Previous Message David E. Wheeler 2009-01-30 18:15:01 Re: Should IS DISTINCT FROM work with ANY()?