From: | Marcos Pegoraro <marcos(at)f10(dot)com(dot)br> |
---|---|
To: | daniel(at)yesql(dot)se |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Trigger position |
Date: | 2021-09-15 12:10:36 |
Message-ID: | CAB-JLwbwC-MAz3F41nszK7JOzwGnKDU3BfsXwfaDYYZ6Fk1g9Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
This problem can raise ... there is a trigger foo using position 1, please
choose another
Atenciosamente,
Em qua., 15 de set. de 2021 às 07:59, Daniel Gustafsson <daniel(at)yesql(dot)se>
escreveu:
> > On 15 Sep 2021, at 12:28, Marcos Pegoraro <marcos(at)f10(dot)com(dot)br> wrote:
>
> > CREATE TRIGGER RECALC_THAT BEFORE UPDATE POSITION 1 ON ORDERS...
> > CREATE TRIGGER DO_OTHER_CALC BEFORE UPDATE POSITION 2 ON ORDERS...
>
> For those not familiar with Firebird: triggers are executing in
> alphabetical
> order within a position number, so it multiple triggers are defined for
> POSITION 1 then they are individually executed alphabetically.
>
> --
> Daniel Gustafsson https://vmware.com/
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Marcos Pegoraro | 2021-09-15 12:12:07 | Re: Trigger position |
Previous Message | Artur Zakirov | 2021-09-15 12:03:25 | Re: BUG #15293: Stored Procedure Triggered by Logical Replication is Unable to use Notification Events |