From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "James B(dot) Byrne" <byrnejb(at)harte-lyne(dot)ca> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Rule or Function and Trigger? |
Date: | 2009-04-03 14:58:24 |
Message-ID: | 1618.1238770704@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"James B. Byrne" <byrnejb(at)harte-lyne(dot)ca> writes:
> I am beginning to migrate some functionality from an application
> prototype into the DBMS. One of these elements is time stamping row
> insertions and updates.
> I have been reading about rules, functions and triggers in regards
> to this issue. So, of course, now I have myself completely
> befuddled. From what I can determine from the documentation, it
> makes little difference to the DBMS whether I set a rule on insert
> and one on update for each table or define a function and set a
> trigger for insert or update on each table.
> If this is indeed the case then which way is the preferred method?
A trigger is very much preferred. Rules are not as easy as they look.
Triggers are a bit more notationally cumbersome, but they tend to
do what you expect without any surprises.
For the problem you mention, a stripped-down version of the first
example here is what you want:
http://www.postgresql.org/docs/8.3/static/plpgsql-trigger.html
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Komaravolu, Satya | 2009-04-03 15:40:17 | constraint trigger |
Previous Message | Sam Mason | 2009-04-03 14:50:00 | Re: reducing IO and memory usage: sending the content of a table to multiple files |