Re: SRF in SFRM_ValuePerCall mode

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "dv (at) nabble" <dvnabble(at)gmail(dot)com>
Cc: "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>, "pgsql-hackers list" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: SRF in SFRM_ValuePerCall mode
Date: 2008-04-29 14:22:34
Message-ID: 977.1209478954@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"dv @ nabble" <dvnabble(at)gmail(dot)com> writes:
> From: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
>> If you're not joining to the function result, and you don't need the
>> ability to determine its result type on the fly, you could declare it
>> as returning a specific rowtype and then call it in the targetlist:
>>
>> select vpc();

> You mean make the function return the only row?

No, I'm pointing out that ValuePerCall SRFs can be called from the
targetlist.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tino Wildenhain 2008-04-29 14:35:41 Re: Protection from SQL injection
Previous Message Tom Dunstan 2008-04-29 14:14:29 Re: Protection from SQL injection