| 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: BEFORE ... Statement-level trigger |
| Date: | 2019-02-18 16:20:43 |
| Message-ID: | CAGBkusfjygjsVokRZNp6fsAzhvJZN_ukSSajsE1CDHTOk2w2dQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Thanks Adrian
I am trying to understand as to how a BEFORE statement-level trigger can be
used. Since it is a trigger, one needs to know which rows are being
affected.
Regards,
Jiten
On Mon 18 Feb, 2019, 9:42 PM Adrian Klaver, <adrian(dot)klaver(at)aklaver(dot)com>
wrote:
> On 2/18/19 4:06 AM, Jitendra Loyal wrote:
> > The behaviour is not clear for BEFORE Statement-level Trigger. This is
> > because transition tables cannot be used. So how does one get access to
> > the rows being affected? It is not documented either.
>
> If you need the row values then use a FOR ROW trigger.
>
> >
> > Thanks
> > Jiten
>
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)aklaver(dot)com
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jitendra Loyal | 2019-02-18 16:23:35 | Re: Statement-level trigger results in recursion |
| Previous Message | Adrian Klaver | 2019-02-18 16:12:19 | Re: BEFORE ... Statement-level trigger |