Re: FOR EACH STATEMENT triggers - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: FOR EACH STATEMENT triggers
Date
Msg-id GNELIHDDFBOCMGBFGEFOKEJICEAA.chriskl@familyhealth.com.au
Whole thread Raw
In response to FOR EACH STATEMENT triggers  (Neil Conway <neilc@samurai.com>)
List pgsql-hackers
Looks pretty sweet, Neil.

Maybe you could look at column triggers while you're at it, per comment on
Compiere page ;)

Triggers

Compiere uses triggers to ensure data consistency. It seems that in general,
Oracle triggers are relatively easy to convert. In addition to the Function
issues, a procedure needs to be crated per trigger. Oracle and PostgreSQL
have slightly different notation of the "new" and "old" references and
INSERTING, etc. PostgreSQL Triggers do not support Column restrictions
(AFTER UPDATE OF column, column ON table).

>         - if the statement effects zero rows, a per-statement trigger
>           is still executed

"affects"  - sorry couldn't help myself :)

Chris



pgsql-hackers by date:

Previous
From: "Christopher Kings-Lynne"
Date:
Subject: Re: [JDBC] PostgreSQL JDBC and sub-select
Next
From: Bruce Momjian
Date:
Subject: Re: [PATCHES] 20020822_02_pitr.patch.gz