From: | Rodrigo De León <rdeleonp(at)gmail(dot)com> |
---|---|
To: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: autoupdating mtime column |
Date: | 2006-08-04 15:39:07 |
Message-ID: | a55915760608040839w1a7caad9vd0aeb4e5e5271905@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
On 8/4/06, David Garamond <davidgaramond(at)gmail(dot)com> wrote:
> On 8/4/06, Richard Huxton <dev(at)archonet(dot)com> wrote:
> > David Garamond wrote:
> > > Dear all,
> > >
> > > Please see SQL below. I'm already satisfied with everything except I
> > > wish in
> > > #4, mtime got automatically updated to NOW() if not explicitly SET in
> > > UPDATE
> > > statement. Is there a way to make the mtime column behave more like I
> > > wanted? Thanks in advance.
> >
> > Just check for OLD.mtime = NEW.mtime, or am I missing something here?
> >
>
>
> How do I differentiate between:
>
> UPDATE t SET mtime=mtime ...;
>
> in which mtime is specifically set and should not change, and
>
> UPDATE t SET foo=bar ...;
>
> in which mtime is not mentioned and should be updated automagically to
> NOW().
How about:
create or replace function
update_times()
returns trigger as $$
begin
if TG_OP='INSERT' then
new.ctime = coalesce(new.ctime,now());
new.mtime = coalesce(new.mtime,now());
elsif TG_OP='UPDATE' then
new.ctime = old.ctime;
new.mtime = now();
end if;
return new;
end;
$$ language plpgsql;
Regards,
Rodrigo
From | Date | Subject | |
---|---|---|---|
Next Message | David Garamond | 2006-08-04 15:51:54 | Re: autoupdating mtime column |
Previous Message | David Garamond | 2006-08-04 15:11:14 | Re: autoupdating mtime column |