From: | Erik Wienhold <ewie(at)ewie(dot)name> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, Lorusso Domenico <domenico(dot)l76(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Strange behaviour on function |
Date: | 2023-07-05 15:33:44 |
Message-ID: | 2063713102.832030.1688571224669@office.mailbox.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> On 05/07/2023 17:16 CEST Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> wrote:
>
> https://www.postgresql.org/docs/current/plpgsql-trigger.html
>
> 1)
> "A trigger function must return either NULL or a record/row value having
> exactly the structure of the table the trigger was fired for."
>
> 2) I am not seeing where you use:
>
> "TG_ARGV[]
>
> Data type array of text; the arguments from the CREATE TRIGGER
> statement. The index counts from 0. Invalid indexes (less than 0 or
> greater than or equal to tg_nargs) result in a null value."
>
> So I don't see how sqlstr is being set?
Domenico did not provide the trigger definition, only function bind_action
which he calls from a trigger function. Also bind_action cannot be a trigger
function because it does not return trigger.
--
Erik
From | Date | Subject | |
---|---|---|---|
Next Message | Lorusso Domenico | 2023-07-05 19:56:21 | Re: Strange behaviour on function |
Previous Message | Adrian Klaver | 2023-07-05 15:16:26 | Re: Strange behaviour on function |