Re: on update set default

From: Doug McNaught <doug(at)wireboard(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Ben-Nes Michael" <miki(at)canaan(dot)co(dot)il>, pgsql-general(at)postgresql(dot)org
Subject: Re: on update set default
Date: 2001-12-10 00:57:47
Message-ID: m3n10r6gdw.fsf@belphigor.mcnaught.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:

> Doug McNaught <doug(at)wireboard(dot)com> writes:
>
> > An AFTER trigger to do this should be pretty easy.
>
> It had better be a BEFORE trigger; AFTER is too late to affect the row
> that will be stored.

Ack, you're right--I was thinking in terms of updating a field in a
different table (don't ask me why). Thanks for the correction.

-Doug
--
Let us cross over the river, and rest under the shade of the trees.
--T. J. Jackson, 1863

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Raymond 2001-12-10 02:07:09 Multiple Instances
Previous Message john 2001-12-10 00:36:25 v6.5.3 and JDBC6.5-1.2 driver FastPath protocol Error: Z