Re: Auto-updated fields - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Auto-updated fields
Date
Msg-id 200901220121.n0M1LfA05793@momjian.us
Whole thread Raw
In response to Re: Auto-updated fields  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: Auto-updated fields  (Robert Treat <xzilla@users.sourceforge.net>)
List pgsql-hackers
Alvaro Herrera wrote:
> Robert Treat wrote:
> > On Thursday 08 May 2008 00:27:10 Tino Wildenhain wrote:
> > > David Fetter wrote:
> 
> Ref: http://archives.postgresql.org/pgsql-hackers/2008-05/msg00198.php
> 
> > > > 1.  Create a generic (possibly overloaded) trigger function, bundled
> > > > with PostgreSQL, which sets a field to some value.  For example, a
> > > > timestamptz version might set the field to now().
> 
> > > Having the pre defined triggers at hand could be useful, especially
> > > for people not writing triggers so often to get used to it but I'm
> > > really not happy with the idea of magic preprocessing.
> 
> > I have a generic version of this in pagila. 
> 
> Now that we have a specific file in core for generic triggers (right now with a
> single one), how about adding this one to it?

Any progress on this?  TODO?

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Pluggable Indexes (was Re: rmgr hooks (v2))
Next
From: Bruce Momjian
Date:
Subject: Re: pg_stats queries versus per-database encodings