Content-Type: text/plain;
  charset="iso-8859-1"
From: Josh Berkus <josh@agliodbs.com>
Reply-To: josh@agliodbs.com
Organization: Aglio Database Solutions
To: Tom Lane <tgl@sss.pgh.pa.us>
Subject: Re: problem fetching currval of sequence
Date: Tue, 6 Aug 2002 11:35:20 -0700
Cc: Charles Hauser <chauser@duke.edu>, pgsql-sql@postgresql.org
References: <web-1602018@davinci.ethosmedia.com>
	<20611.1028651144@sss.pgh.pa.us>
In-Reply-To: <20611.1028651144@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200208061135.20799.josh@agliodbs.com>


Tom,

> Huh?  AFAIR it's always worked the way it does now (and a quick review
> of the CVS logs for sequence.c backs up my recollection).

No, back in 7.1.0 I was able to call CURRVAL without having previously call=
ed=20
NEXTVAL, and it would give me the "current" sequence value; that is, the sa=
me=20
result value as (NEXTVAL() - 1);   I wouldn't mind having a new function th=
at=20
does this; I can understand making a distinction between the pre-session=20
CURRVAL, and the general current value.

> Such a front end would be too broken to consider using anyway: if you
> cannot wrap several related commands into a transaction, you cannot use
> a database the way it's intended to be used.  The connection-pooling
> front ends that I know about all give you dedicated use of a connection
> for at least the length of a transaction block, so the secret to using
> currval is "do it in the same transaction block as you call nextval in".

Me, I use functions.


--=20
-Josh Berkus
 Aglio Database Solutions
 San Francisco