| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "Neil Conway" <neilc(at)samurai(dot)com>, "PostgreSQL Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: FOR EACH STATEMENT triggers |
| Date: | 2002-11-15 03:16:05 |
| Message-ID: | GNELIHDDFBOCMGBFGEFOKEJICEAA.chriskl@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-11-15 04:07:19 | Re: [PATCHES] 20020822_02_pitr.patch.gz |
| Previous Message | Christopher Kings-Lynne | 2002-11-15 03:13:58 | Re: [JDBC] PostgreSQL JDBC and sub-select |