From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: PFC <lists@boutiquenumerique.com>
Cc: Michael Fuhr <mike@fuhr.org>
Cc: lmeadors@apache.org
Cc: pgsql-sql@postgresql.org
Subject: Re: getting back autonumber just inserted
Date: Thu, 7 Jul 2005 18:42:27 -0400
Message-ID: <20050707224227.GB23230@alvh.no-ip.org> (raw)
In-Reply-To: <op.stkdygr8th1vuj@localhost>
References: <42CD6B58.6060508@techevolution.be>
<20050707201433.94901.qmail@web41013.mail.yahoo.com>
<20050707203715.GA26528@winnie.fuhr.org>
<a10a823c05070713473add03d7@mail.gmail.com>
<20050707205725.GA28200@winnie.fuhr.org>
<op.stkdygr8th1vuj@localhost>
On Fri, Jul 08, 2005 at 12:26:30AM +0200, PFC wrote:
>
> >That's a different issue than whether currval() is subject to
> >interference from other transactions. And just wait until PostgreSQL
> >8.1 comes out and people start using lastval() -- then it could get
> >*really* confusing which sequence value you're getting.
>
> What happens if an INSERT trigger inserts something into another
> table which also has a sequence ?
Using what, lastval()? The app will get very confused, because it'll
get the value from the sequence used in the trigger. Using currval
there is no problem, but you already knew that.
--
Alvaro Herrera (<alvherre[a]alvh.no-ip.org>)
"Hay quien adquiere la mala costumbre de ser infeliz" (M. A. Evans)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: alvherre@alvh.no-ip.org, lists@boutiquenumerique.com, mike@fuhr.org, lmeadors@apache.org
Subject: Re: getting back autonumber just inserted
In-Reply-To: <20050707224227.GB23230@alvh.no-ip.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox