Re: SELECTing from a function where i don't want the results

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Holger Jakobs <holger(at)jakobs(dot)com>
Cc: "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: SELECTing from a function where i don't want the results
Date: 2020-07-08 00:07:20
Message-ID: CAKFQuwYKshD9ZDtQV=mYWSxJL8-86h_kQM7ysmaSZuckuiQxLw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Tuesday, July 7, 2020, Holger Jakobs <holger(at)jakobs(dot)com> wrote:

> You could combine the result with a NULL value, as any operations with
> NULL result in NULL.
>
> SELECT mydelete(r) + NULL FROM sometable;
>
So now you have 100 rows containing null (assuming that indeed function
result + unknown means something and you don’t just get an error) which is
no better than what is the probably 100 rows of void output the OP is
complaining about.

David J.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Wells Oliver 2020-07-08 00:10:20 Re: SELECTing from a function where i don't want the results
Previous Message Holger Jakobs 2020-07-07 22:38:18 Re: SELECTing from a function where i don't want the results