Re: Auto-updated fields

From: David Fetter <david(at)fetter(dot)org>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, pgsql-hackers(at)postgresql(dot)org, Tino Wildenhain <tino(at)wildenhain(dot)de>
Subject: Re: Auto-updated fields
Date: 2009-02-04 21:56:11
Message-ID: 20090204215611.GC21988@fetter.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Feb 04, 2009 at 01:23:04PM -0500, Bruce Momjian wrote:
> Robert Treat wrote:
> > On Wednesday 21 January 2009 20:21:41 Bruce Momjian wrote:
> > > 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?
> >
> > I think this is a TODO, but not sure who is working on it or what needs to be
> > done. The generic version in pagila is perhaps not generic enough:
> >
> > CREATE FUNCTION last_updated() RETURNS trigger
> > AS $$
> > BEGIN
> > NEW.last_update = CURRENT_TIMESTAMP;
> > RETURN NEW;
> > END $$
> > LANGUAGE plpgsql;
> >
> > It requires you name your column last_update, which is what the naming
> > convention is in pagila, but might not work for everyone. Can someone work
> > with that and move forward? Or maybe give a more specific pointer to the
> > generic trigger stuff (I've not looked at it before)
>
> Well, I thought it was a good idea, but no one seems to want to do the
> work.

It's a very short piece of work, but it's new work, and I can't in
good conscience propose including it in the 8.4 release :(

Cheers,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com

Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2009-02-04 22:06:55 Re: Bugs during ProcessCatchupEvent()
Previous Message Robert Haas 2009-02-04 21:49:37 Re: [PATCHES] GIN improvements