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 17:48:34 -0500
Message-ID: <26587.1067986114@sss.pgh.pa.us> (raw)
In-Reply-To: <20031104223319.GA2879@clueinc.net>
References: <20031104223319.GA2879@clueinc.net>
Jamie Lawrence <postgres@jal.org> writes:
> I had thought that if moddate isn't included in an insert or update,
> that it would be null in the NEW context,
No, it would be whatever the value to be assigned to the column would
be, if the trigger were not present. In particular, during an UPDATE
it's going to contain the old value of the field. In an INSERT it would
be whatever the column's default value is.
I am not sure what your intention is here. If you want the trigger to
force the field to current time, it can certainly do that. If you want
the user to control whether the field is updated, why do you need a
trigger at all?
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: <26587.1067986114@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