Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.9.3/8.9.3) with ESMTP id LAA37821 for ; Fri, 22 Oct 1999 11:46:19 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id LAA20776; Fri, 22 Oct 1999 11:45:27 -0400 (EDT) To: grant@intekom.com cc: pgsql-sql@postgreSQL.org Subject: Re: [SQL] Adding a rule to update a last_changed field In-reply-to: Your message of Fri, 22 Oct 1999 08:03:05 -0700 <221099295.28982@212.53.64.128> Date: Fri, 22 Oct 1999 11:45:26 -0400 Message-ID: <20774.940607126@sss.pgh.pa.us> From: Tom Lane grant@intekom.com writes: > I'm trying to use a rule to maintain a last_changed field. Use a trigger, not a rule. You can adjust the last_changed field before the tuple is stored that way. There's an example in the manual's discussion of triggers. regards, tom lane