Re: PL/pgSQL PERFORM with CTE - Mailing list pgsql-hackers

From David E. Wheeler
Subject Re: PL/pgSQL PERFORM with CTE
Date
Msg-id 3F071179-7CE4-4E07-8D8A-467448BAF581@justatheory.com
Whole thread Raw
In response to Re: PL/pgSQL PERFORM with CTE  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: PL/pgSQL PERFORM with CTE  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
On Aug 20, 2013, at 3:05 PM, Pavel Stehule <pavel.stehule@gmail.com> wrote:

> When you would to ignore result, then you should to use a PERFORM - actually, it is limited now and should be fixed.
Haveno problem with it. 

Glad to have you on board. :-)

> I don't would to enable a free unbound statement that returns result.

I have no pony in that race. I think it is useful, though I prefer to unit test things enough that I would be fine
withoutit. 

But even without it, there may be times when I want to discard a result in a function that *does* return a value --
likelya different value. So there needs to be a way to distinguish statements that should return a value and those that
donot. 

Best,

David




pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review])
Next
From: Pavel Stehule
Date:
Subject: Re: PL/pgSQL PERFORM with CTE