Re: Problems with transactions and sequences - Mailing list pgsql-general

From lanette@poynter.org (Lanette Miller)
Subject Re: Problems with transactions and sequences
Date
Msg-id 6ec1a27c.0308281137.1862dfd9@posting.google.com
Whole thread Raw
In response to Problems with transactions and sequences  (Sune Nielsen <sunegn@image.dk>)
List pgsql-general
> You need to extract the current val first and explicitly use it in insert
> statement. That way you won't have to produce work-arounds later..
This statement is wrong. If you were going to use this method (
getting the value first - then setting it), I believe you would need
to call nextval not currval.

Lanette

shridhar_daithankar@persistent.co.in ("Shridhar Daithankar") wrote in message news:<3F4E650B.3698.795CE8@localhost>...
> On 28 Aug 2003 at 14:35, Sune Nielsen wrote:
> > INSERT INTO Users (name) VALUES ('JohnDoe');
> > SELECT CURRVAL('users_bid_seq');
> >
> > This works perfectly(!), but my project involves multiple simultanous
> > users so I have to use transactions like this:
> >
> > BEGIN;
> > INSERT INTO Users (name) VALUES ('JohnDoe');
> > SELECT CURRVAL('users_bid_seq');
> > COMMIT;
>
>
> Bye
>  Shridhar

pgsql-general by date:

Previous
From: Mike Mascari
Date:
Subject: Re: left outer join terrible slow compared to inner join
Next
From: jason dang
Date:
Subject: Install PostgreSQL on AIX 5.1