| From: | "Bolden, Thomas" <tbolden(at)ded(dot)state(dot)mo(dot)us> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | trigger column update |
| Date: | 2002-08-12 20:29:26 |
| Message-ID: | D2421549D378D3119D4E000629840F070741F3CD@ECOEXCHG |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
I am porting over a trigger from oracle.
"CREATE TRIGGER TR_CLUSCODE_UPD AFTER UPDATE OF STFIPS, CLUSCODE,
CLUSTITLE, CLUSDESC ON CLUSCODE
FOR EACH ROW EXECUTE"
The trigger is column dependent and according to the online docs.
"
The CREATE TRIGGER statement in PostgreSQL implements a subset of the SQL99
standard. The following functionality is missing:
*
SQL99 allows triggers to fire on updates to specific columns (e.g., AFTER
UPDATE OF col1, col2).
"
anyone know a work around.
Thomas Bolden
Department of Economic Development
GIS Programmer
(573) 751-3672
tbolden(at)ded(dot)state(dot)mo(dot)us
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2002-08-12 21:55:54 | Re: [GENERAL] workaround for lack of REPLACE() function |
| Previous Message | Peter Eisentraut | 2002-08-12 20:07:18 | Re: [GENERAL] Linux Largefile Support In Postgresql RPMS |