| From: | frbn <frbn(at)efbs-seafrigo(dot)fr> |
|---|---|
| To: | "Bolden, Thomas" <tbolden(at)ded(dot)state(dot)mo(dot)us> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: trigger column update |
| Date: | 2002-08-13 07:02:04 |
| Message-ID: | 3D58AEEC.30307@efbs-seafrigo.fr |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Bolden, Thomas a écrit:
> 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.
you can put the columns you want to "trigger" in another table
and put a trigger on the update of this table.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | mixo | 2002-08-13 08:13:18 | Re: unexpected results |
| Previous Message | Graeme Merrall | 2002-08-13 05:43:54 | trees - tree, ltree or other? |