Re: set-valued function called in context that cannot accept a set

From: "Eric B(dot) Ridge" <ebr(at)tcdi(dot)com>
To: depesz(at)depesz(dot)com
Cc: rod(at)iol(dot)ie, pgsql-general(at)postgresql(dot)org
Subject: Re: set-valued function called in context that cannot accept a set
Date: 2009-03-06 21:10:59
Message-ID: 7AF28A66-D3D4-4700-94FC-6A3DB8BC9083@tcdi.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Ben Chobot 2009-03-06 21:22:49 Re: Maximum transaction rate
Previous Message hubert depesz lubaczewski 2009-03-06 20:49:23 Re: set-valued function called in context that cannot accept a set