| From: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Marko Tiikkaja <marko(at)joh(dot)to>, pgsql-hackers Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PL/pgSQL PERFORM with CTE |
| Date: | 2013-08-20 13:43:21 |
| Message-ID: | 884E56B9-1937-4594-958D-A26306FC0B15@justatheory.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Aug 20, 2013, at 3:38 PM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
> pg_notify returns void, so there are no necessary casting to void
>
> so enhanced check - so all returned columns are void should be enough
What if I call another function I wrote myself that returns an INT, but I do not care about the INT? Maybe that function does the insert and returns the number of inserted rows.
I can think of all kinds of reasons this might be the case; whether they are good or bad approaches is immaterial: sometimes you work with what you have.
I am find with PERFORM to determine when a query's results should be discarded. I just think it needs to cover a few more cases.
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2013-08-20 13:46:54 | Re: PL/pgSQL PERFORM with CTE |
| Previous Message | Andrew Dunstan | 2013-08-20 13:42:16 | Re: Fix Windows socket error checking for MinGW |