From: Jamie Lawrence <jal@jal.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-sql@postgresql.org
Subject: Re: Problems with NEW.* in triggers
Date: Tue, 4 Nov 2003 19:16:53 -0500
Message-ID: <20031105001653.GD2879@clueinc.net> (raw)
In-Reply-To: <27275.1067991046@sss.pgh.pa.us>
References: <20031104223319.GA2879@clueinc.net>
<26587.1067986114@sss.pgh.pa.us>
<20031104231402.GB2879@clueinc.net>
<27275.1067991046@sss.pgh.pa.us>
On Tue, 04 Nov 2003, Tom Lane wrote:
> Jamie Lawrence <postgres@jal.org> writes:
> > I don't understand why moddate isn't getting set to now() in the above.
>
> Josh fingered the problem there --- you need a BEFORE trigger if you
> want to affect the data that will be stored. I had missed that little
> mistake :-(
Yep. Many thanks to both of you.
-j
--
Jamie Lawrence jal@jal.org
If built in great numbers, motels will be used for nothing but illegal
purposes.
- J. Edgar Hoover
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: jal@jal.org, tgl@sss.pgh.pa.us
Subject: Re: Problems with NEW.* in triggers
In-Reply-To: <20031105001653.GD2879@clueinc.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox