Message-ID: <5384BBE5.5020409@noao.edu>
Date: Tue, 27 May 2014 09:23:01 -0700
From: Steve Wampler <swampler@noao.edu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: Andreas Kretschmer <andreas@a-kretschmer.de>,
 Postgres-SQL <pgsql-sql@postgresql.org>
Subject: Re: Set flag column on update if other columns change?
References: <5384B683.9030505@noao.edu>
 <1124372711.31798.1401207718005.open-xchange@oxweb02.ims-firmen.de>
In-Reply-To: 
 <1124372711.31798.1401207718005.open-xchange@oxweb02.ims-firmen.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-sql-owner@postgresql.org

On 05/27/2014 09:21 AM, Andreas Kretschmer wrote:
>> Steve Wampler <swampler@noao.edu> hat am 27. Mai 2014 um 18:00 geschrieben:
>> I've got a table where updates that actually change things need to
>> record in the row that the row has been modified.  I'm assuming that a
>> trigger function (OK to be plpgsql, performance isn't much of
>> an issue) is the best way to do this, but haven't done much
>> with trigger functions.  Can someone give me some pointers
>> on how this might be accomplished?  I have to check for
>> changes in a subset of the columns (e.g. ignore timestamps, etc.).
>
> Trigger BEFORE, compare NEW. with OLD.. Easy.

Thanks!  I didn't know about OLD...


-- 
Steve Wampler -- swampler@noao.edu
The gods that smiled on your birth are now laughing out loud.


-- 
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql