| From: | Mark <nvpostgres(at)gmail(dot)com> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Debugging --- ERROR: function does not exist |
| Date: | 2026-10-26 15:26:13 |
| Message-ID: | CAAm-KOt6H4oECXr896cp2=txadJkMp_pQ2_78AcKUfZiMdU98Q@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> Given that OUT is basically an alternate form of RETURNS why do you want
> to supply the OUT values to the function/procedure SELECT/CALL in the
> first place?
>
> That would be something the function/procedure does internally using the
> IN values, where IN is either explicitly stated or implied by a lack of
> an IN/OUT/INOUT declaration.
>
>
Honestly I don't know at the moment, guess it is a stylistic choice, along
with the choice to use a PROCEDURE vs a FUNCTION (which I do not know that
much about, other than what I have learned in this thread)
I guess with the RETURNS it make the DECLARE section cleaner and with the
PROCEDURE it make the body of the code cleaner
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2026-10-26 16:06:11 | Re: Debugging --- ERROR: function does not exist |
| Previous Message | Mark | 2026-10-26 15:21:59 | Re: Debugging --- ERROR: function does not exist |