Re: set-valued function called in context that cannot accept a set - Mailing list pgsql-general

From Eric B. Ridge
Subject Re: set-valued function called in context that cannot accept a set
Date
Msg-id 7AF28A66-D3D4-4700-94FC-6A3DB8BC9083@tcdi.com
Whole thread Raw
In response to Re: set-valued function called in context that cannot accept a set  (hubert depesz lubaczewski <depesz@depesz.com>)
List pgsql-general
On Mar 6, 2009, at 3:49 PM, hubert depesz lubaczewski wrote:

> On Fri, Mar 06, 2009 at 03:33:30PM -0500, Eric B. Ridge wrote:
>> So my question is really, what's the difference and why doesn't this
>> work with PL/PGSQL functions?
>
> because it is long-time limitation of setof-returning plplsql
> functions
> (i think all pl/*).
> it is removed in 8.4

I also now see that 8.4 has its own unnest function built in.
http://developer.postgresql.org/pgdocs/postgres/functions-array.html

One more reason to look forward to 8.4, I suppose.  Until then, I
suppose I'm sticking with my custom C library.  :(

Thanks!

eric

pgsql-general by date:

Previous
From: hubert depesz lubaczewski
Date:
Subject: Re: set-valued function called in context that cannot accept a set
Next
From: Ben Chobot
Date:
Subject: Re: Maximum transaction rate