From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: array_map not SQL accessible? |
Date: | 2009-01-30 18:35:48 |
Message-ID: | 20090130183548.GA7428@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> 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.)
regproc maybe?
> > 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)
Hmm, I'll have a look at this.
--
Alvaro Herrera http://www.PlanetPostgreSQL.org/
"Linux transformó mi computadora, de una `máquina para hacer cosas',
en un aparato realmente entretenido, sobre el cual cada día aprendo
algo nuevo" (Jaime Salinas)
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2009-01-30 18:56:29 | Re: array_map not SQL accessible? |
Previous Message | Tom Lane | 2009-01-30 18:17:47 | Re: array_map not SQL accessible? |