| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | PegoraroF10 <marcos(at)f10(dot)com(dot)br> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Trigger bug ? |
| Date: | 2019-05-22 22:01:06 |
| Message-ID: | CAKFQuwYH5u0b29X23Dad1ZTvgm=J2mAEh83Nz6Yrf4aiWB_ARw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, May 22, 2019 at 2:33 PM PegoraroF10 <marcos(at)f10(dot)com(dot)br> wrote:
> We forgot FOR EACH ROW/STATEMENT when created our trigger.
>
> On docs it´s written {ROW/STATEMENT} between {}, so it´s needed. But why
> did
> it accepted our command to create that trigger ?
>
You only partially absorbed the syntax doc for that...in full it reads:
...
[ FOR [ EACH ] { ROW | STATEMENT } ]
You omitted the whole thing which is allowed.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Perumal Raj | 2019-05-22 22:15:53 | Re: Centos : Load Average :OS Process Name : migration/1, migration/2 , migration/n |
| Previous Message | Adrian Klaver | 2019-05-22 21:37:35 | Re: Trigger bug ? |