On Thu, Oct 20, 2011 at 3:01 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
>> I didn't design a PERFORM statement. There is two views - somebody
>> from sybase's family know so SELECT without into is forwarded to
>> client. This functionality is missing on Oracle's family. Is true so
>> PERFORM statement is strange, but maybe it's open door for sybase's
>> functionality that was not implemented ever.
> I cannot imagine that we'd ever make SELECT inside a plpgsql function
> act like that. Functions have no business directly transmitting
> information to the client; if they tried, they'd most likely just break
> the FE/BE protocol.
> There might be use for such a thing in a hypothetical "real stored
> procedure language" where the code is executing in a context entirely
> different from what Postgres functions run in ... but that language
> would be something different from plpgsql.
small aside: I disagreed with this point a while back but I'm coming
around to your point of view...
In response to
pgsql-bugs by date
|Next:||From: Pavel Stehule||Date: 2011-10-20 21:25:28|
|Subject: Re: Can't use WITH in a PERFORM query in PL/pgSQL?|
|Previous:||From: Tom Lane||Date: 2011-10-20 20:01:45|
|Subject: Re: Can't use WITH in a PERFORM query in PL/pgSQL? |