| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, pgsql-hackers(at)postgresql(dot)org, Tino Wildenhain <tino(at)wildenhain(dot)de>, David Fetter <david(at)fetter(dot)org> |
| Subject: | Re: Auto-updated fields |
| Date: | 2009-01-22 01:21:41 |
| Message-ID: | 200901220121.n0M1LfA05793@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2009-01-22 01:29:37 | Re: pg_stats queries versus per-database encodings |
| Previous Message | Simon Riggs | 2009-01-22 01:02:02 | Re: Pluggable Indexes (was Re: rmgr hooks (v2)) |