Re: SELECTing from a function where i don't want the results - Mailing list pgsql-admin

From David G. Johnston
Subject Re: SELECTing from a function where i don't want the results
Date
Msg-id CAKFQuwY85T8D927HMfQHZ15gD_BNfyzsu=ZPGgxofohXruWiNw@mail.gmail.com
Whole thread Raw
In response to Re: SELECTing from a function where i don't want the results  (Scott Ribe <scott_ribe@elevated-dev.com>)
List pgsql-admin
On Tuesday, July 7, 2020, Scott Ribe <scott_ribe@elevated-dev.com> wrote:
> On Jul 7, 2020, at 7:14 PM, Wells Oliver <wells.oliver@gmail.com> wrote:
>
> Sorry guys, it works exactly the way I want, just wanted to suppress its output when called for thousands of rows. Apologies if I wasn't clear enough.

It seems that it doesn't work the way you want, because it can output thousands of rows ;-)

You all may want to re-read the original post before commenting further.  I’m finding nothing particularly unusual about this setup.  Sure, multiple delete using commands or cascade delete may be a bit more performant if the api described in the OP is sufficiently fast it is definitely the easiest to program against.

David J.

pgsql-admin by date:

Previous
From: Scott Ribe
Date:
Subject: Re: SELECTing from a function where i don't want the results
Next
From: Jim Gmail
Date:
Subject: Re: SELECTing from a function where i don't want the results