Re: currval() within one statement

From: Richard Huxton <dev(at)archonet(dot)com>
To: silly_sad <sad(at)bankir(dot)ru>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: currval() within one statement
Date: 2008-01-22 12:18:47
Message-ID: 4795DF27.5030602@archonet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

silly_sad wrote:
>
> id default value is always set by the trigger before insert on each
> table for each row.
>
> The particular subproblem is to
> insert one record into ttt1
> and then insert corresponding record into ttt,
> ___This is the place to use currval.

I'd be tempted to turn it the other way around and have an AFTER trigger
that just uses NEW.id as the value to put into "ttt".

The reason to use an AFTER trigger is that you know the value can't be
changed at that point, whereas with a BEFORE trigger it might. In your
case it doesn't matter, but it's probably a good idea to be consistent
in these things.

--
Richard Huxton
Archonet Ltd

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Michael Glaesemann 2008-01-22 12:42:20 Re: TIMESTAMP comparison problem
Previous Message hubert depesz lubaczewski 2008-01-22 11:27:54 Re: currval() within one statement