simulating INSERT return values with default values of sequences

Поиск
Список
Период
Сортировка
От Thomas F. O'Connell
Тема simulating INSERT return values with default values of sequences
Дата
Msg-id 3D3C5A9E.2080903@monsterlabs.com
обсуждение исходный текст
Ответы Re: simulating INSERT return values with default values  (Darren Ferguson <darren@crystalballinc.com>)
Re: simulating INSERT return values with default values of sequences  (Andrew Sullivan <andrew@libertyrms.info>)
Список pgsql-general
i didn't see this question asked (or answered in the mailing lists), but
it seems like it would be an FAQ...

anyway, i'm just wondering if there's a slick way of any sort to be able
to have a value generated from an INSERT available for immediate and
secure re-use.

for example, if i have

CREATE SEQUENCE foo_id_seq;
CREATE TABLE foo (
    id int2 primary key default nextval( 'foo_id_seq' ),
    bar text
);

and then later have

INSERT INTO foo( bar ) VALUES( 'baz' );

is there any way safely to know what was inserted into the "id" field
without encapsulating the INSERT statement in a transaction with
whatever function needed that value?

i'm guessing a transaction probably makes the most sense, right?

e.g.,

BEGIN WORK;
INSERT INTO foo( bar ) VALUES( 'baz' );
UPDATE foo SET bar = 'ola' WHERE id = ( SELECT last_value FROM foo_id_seq );
END WORK;

if so, then i guess the next question is: is there a preference between
a statement like

UPDATE foo SET bar = 'ola' WHERE id = ( SELECT last_value FROM foo_id_seq );

and

UPDATE foo SET bar = 'ola' WHERE id = ( SELECT MAX( id ) FROM foo );

thanks!

-tfo


В списке pgsql-general по дате отправления:

Предыдущее
От: Stephan Szabo
Дата:
Сообщение: Re: viewing/altering the "ON DELETE CASCADE" constraint
Следующее
От: Oliver Elphick
Дата:
Сообщение: Re: sequence scan, but indexed tables