From: | Jitendra Loyal <jitendra(dot)loyal(at)gmail(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Statement-level trigger results in recursion |
Date: | 2019-02-18 23:39:16 |
Message-ID: | CAGBkusc4rhvTL7D4zmrXK2WYGACU+xreXNfy5eDX6ecO+K1UTw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thanks for all your efforts. I appreciate it.
Let us wait and see if someone can enlighten us, or you locate the
conversation.
Thanks once again
Regards,
Jiten
On Tue 19 Feb, 2019, 3:19 AM Adrian Klaver, <adrian(dot)klaver(at)aklaver(dot)com>
wrote:
> On 2/18/19 9:07 AM, Jitendra Loyal wrote:
> > I do understand that the statement level trigger will be executed once
> > before the operation. My point is.. if one does not know the rows, what
> > kind of use it can be put to. What is the use case? Like in after
> > triggers, one gets the rows in transition tables, how does one do with
> > vefore trigger.
>
> Use FOR EACH ROW.
>
> Why you cannot use a FOR EACH STATEMENT trigger is something I thought I
> remember being discussed on the list before. Unfortunately I cannot find
> that conversation at the moment. Someone else will need to weigh in on
> this.
>
> >
> > Thanks and regards,
> > Jiten
>
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)aklaver(dot)com
>
From | Date | Subject | |
---|---|---|---|
Next Message | Jitendra Loyal | 2019-02-18 23:46:05 | Re: BEFORE ... Statement-level trigger |
Previous Message | Thomas Munro | 2019-02-18 22:14:16 | Re: WSL (windows subsystem on linux) users will need to turn fsync off as of 11.2 |