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

From Dennis Gearon
Subject Re: Problems with transactions and sequences
Date
Msg-id 3F4E1E47.1080804@fireserve.net
Whole thread Raw
In response to Re: Problems with transactions and sequences  ("Shridhar Daithankar" <shridhar_daithankar@persistent.co.in>)
Responses Re: Problems with transactions and sequences  ("Shridhar Daithankar" <shridhar_daithankar@persistent.co.in>)
Re: Problems with transactions and sequences  (Bruno Wolff III <bruno@wolff.to>)
List pgsql-general
if one gives a value for the seirial field, the trigger for the serial
on that table doesn't generate another value?

Shridhar Daithankar wrote:

>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;
>>
>>
>
>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..
>
>Bye
> Shridhar
>
>--
>Vulcans do not approve of violence.        -- Spock, "Journey to Babel", stardate
>3842.4
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 4: Don't 'kill -9' the postmaster
>
>
>


pgsql-general by date:

Previous
From: Dennis Gearon
Date:
Subject: Re: Functions have 32 args limt ???
Next
From: "Marie G. Tuite"
Date:
Subject: Re: before trigger problem