From: | Bradley Baetz <bbaetz(at)student(dot)usyd(dot)edu(dot)au> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Rod Taylor <rbt(at)zort(dot)ca>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
Subject: | Re: [INTERFACES] [pgaccess-users] RE: bugzilla.pgaccess.org |
Date: | 2002-07-11 03:29:26 |
Message-ID: | Pine.LNX.4.44.0207111328310.30839-100000@tomato.home |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 10 Jul 2002, Tom Lane wrote:
> Bradley Baetz <bbaetz(at)student(dot)usyd(dot)edu(dot)au> writes:
> > I'm referring to the mysql |timestamp| type, which will update that
> > column's contents to |now()| when any UPDATE is given for that partcular
> > row, unless the column was assigned to. I don't know how to handle the
> > last part in a trigger.
>
> It'd probably be close enough to have an UPDATE trigger that does
>
> if (new.timestamp = old.timestamp)
> new.timestamp = now();
Nope, because the documented way of making sure that the field doens't
change is to use |UPDATE foo SET bar=bar ....|, and thats what bz uses.
Don't worry about this, though - we will hpefully be removing this
'feature' soon.
Bradley
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Kings-Lynne | 2002-07-11 03:30:41 | Re: Should this require CASCADE? |
Previous Message | Tom Lane | 2002-07-11 03:25:05 | Re: [INTERFACES] [pgaccess-users] RE: bugzilla.pgaccess.org |