From: | David Fetter <david(at)fetter(dot)org> |
---|---|
To: | PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Auto-updated fields |
Date: | 2008-05-07 22:04:49 |
Message-ID: | 20080507220449.GG15867@fetter.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Folks,
A co-worker pointed out to me that MySQL has a feature that, properly
implemented and maybe extended, could be handy, namely what MySQL
calls a "timestamp" field, so here's a proposal:
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().
2. Have some kind of pre-processing of CREATE and ALTER statements on
tables which would attach the above function to the field at hand,
something like:
CREATE TABLE foo(
last_updated TIMESTAMPTZ_UPDATED(),
...
);
which would turn last_updated into a TIMESTAMPTZ with the expected
behavior on UPDATEs.
What do folks think of this idea?
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
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2008-05-07 22:22:03 | Re: [HACKERS] bug in numeric_power() function |
Previous Message | Alvaro Herrera | 2008-05-07 21:55:43 | Re: printTable API (was: Show INHERIT in \du) |