Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
currval() within one statement
- From: silly_sad <sad(at)bankir(dot)ru>
- To: pgsql-sql(at)postgresql(dot)org
- Subject: currval() within one statement
- Date: Tue, 22 Jan 2008 10:16:30 +0300
- Message-id: <4795984E.7030904@bankir.ru> <text/plain>
Helois it expected that the currval() changes its value between calls within one statement ?
Look the following call:
INSERT INTO ttt (a,b) SELECT currval('ttt_id_seq'), 'const' FROM ttt2;
Where the trigger before insert on ttt is defined and this trigger calls
nextval('ttt_id_seq').
I was surprised having different values of currval() in ttt.a Is this the normal behavior ? Where is it described ?
- Follow-Ups:
- Re: currval() within one statement
- From: hubert depesz lubaczewski
- Re: currval() within one statement
- From: A. Kretschmer
- Re: currval() within one statement
- Prev by Date: Re: improvements to query with hierarchical elements
- Next by Date: Re: currval() within one statement
- Previous by thread: Having elements of an int[]-array reference other tables
- Next by thread: Re: currval() within one statement
- Indexes: