From: | Alban Hertroys <alban(at)magproductions(dot)nl> |
---|---|
To: | Jason Lee <lee(at)iecokc(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Trigger Question |
Date: | 2007-03-14 15:42:48 |
Message-ID: | 45F817F8.5020102@magproductions.nl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Jason Lee wrote:
> I'm trying to write a trigger that updates a date_changed field on a
> record anytime that record is updated. I have a function written, and
> the trigger created, but everytime I update the record, I get a
> recursion limit error. It appears that the action performed by my
You probably want to use a BEFORE UPDATE trigger and assign now() to
NEW.date_changed.
> trigger is causing the trigger to fire. How do I avoid that. For the
> record, here's my function (modeled after a trigger that works on SQL
> Server. I'm pretty much a noob with plpgsql :)
>
> declare begin
> update unit_specification set date_changed = now() from
> unit_specification us where us.id = NEW.id;
> RETURN NEW;
> end;
>
> With the trigger created with
>
> CREATE TRIGGER update_changed_ts AFTER INSERT OR UPDATE
> ON unit_specification FOR EACH ROW
> EXECUTE PROCEDURE public.update_unit_spec_changed_date();
>
> Thanks for the help. :)
>
> -----
> Jason Lee, SCJP
> Senior Software Engineer
> http://www.iec-okc.com <http://www.iec-okc.com/>
>
>
--
Alban Hertroys
alban(at)magproductions(dot)nl
magproductions b.v.
T: ++31(0)534346874
F: ++31(0)534346876
M:
I: www.magproductions.nl
A: Postbus 416
7500 AK Enschede
// Integrate Your World //
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-03-14 15:44:22 | Re: Multiple TRIGGERs and OLD versus NEW "records" |
Previous Message | Jason Lee | 2007-03-14 15:40:54 | Re: Trigger Question |