Re: Problems with transactions and sequences
От | Dennis Gearon |
---|---|
Тема | Re: Problems with transactions and sequences |
Дата | |
Msg-id | 3F4E1E47.1080804@fireserve.net обсуждение исходный текст |
Ответ на | Re: Problems with transactions and sequences ("Shridhar Daithankar" <shridhar_daithankar@persistent.co.in>) |
Ответы |
Re: Problems with transactions and sequences
Re: Problems with transactions and sequences |
Список | 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 по дате отправления: