From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jamie Lawrence <postgres@jal.org>
Cc: pgsql-sql@postgresql.org
Subject: Re: Problems with NEW.* in triggers
Date: Tue, 04 Nov 2003 19:10:46 -0500
Message-ID: <27275.1067991046@sss.pgh.pa.us> (raw)
In-Reply-To: <20031104231402.GB2879@clueinc.net>
References: <20031104223319.GA2879@clueinc.net>
<26587.1067986114@sss.pgh.pa.us>
<20031104231402.GB2879@clueinc.net>
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 :-(
regards, tom lane
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: tgl@sss.pgh.pa.us, postgres@jal.org
Subject: Re: Problems with NEW.* in triggers
In-Reply-To: <27275.1067991046@sss.pgh.pa.us>
* 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